[CVE-2026-72157][MODERATE 7.0] net: thunderbolt: Fix frags[] overflow by bounding frame_count

[CVE-2026-72157][MODERATE 7.0] net: thunderbolt: Fix frags[] overflow by bounding frame_count

[AL-KERNEL]

CVE: CVE-2026-72157
Priority: MODERATE 7.0
AL-KERNEL base severity: MODERATE
KPANIC flag: YES
Patch: net: thunderbolt: Fix frags[] overflow by bounding frame_count
Commit: 2b3b4e5ff5a58ad32817824b0310e63908b12052
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=2b3b4e5ff5a58ad32817824b0310e63908b12052
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72157
Analysis date: Sun, 16 Aug 2026 06:07:01 -0400
ActionableScore: 7
ActionableScore lower bound: 6
Actionable bucket: Strong Important candidate / Actionable Moderate at minimum
Manual review required: YES

Summary:
A malicious ThunderboltIP peer can send an oversized multi-frame packet that makes `skb_add_rx_frag()` write past `skb_shinfo()->frags[]`, causing adjacent kernel memory corruption with at least crash impact and plausible privilege-escalation concern.

======================================================================
ABOUT THIS REPORT
======================================================================

The original Linux kernel CVE announcement for CVE-2026-72157 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72157

The original announcement does not normally provide a security severity
estimate, CVSS assessment, or enough information to determine whether the
reported kernel bug represents a practically relevant security issue.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin. It combines
an autonomous classifier with LLM-assisted technical analysis and a
separate ActionableScore mechanism.

The purpose of this report is to prioritize Linux kernel CVEs before
manual review, identify cases that require prompt investigation, and
support automatic closure of issues that are unlikely to have meaningful
security impact.

Published priority for this report: MODERATE 7.0
Manual review required: YES

A detailed explanation of the methodology and priority rules is included
at the end of this message.

======================================================================
AL-KERNEL CLASSIFICATION RESULT
======================================================================

CVE-2026-72157	MODERATE	CHECK WITH IMPACT FROM ORIG NN LOW	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H';*CWE-787;CWE-129;*CWE-20;Other CVSS 'AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H';BEST CVSS score: '8.8';DESCR 'ThunderboltIP receive processing can overflow the skb shared info frags array because tbnet_poll stores the first frame in the linear skb area and each additional frame as a page fragment, while the peer supplied frame_count was only bounded to 64. A malicious ThunderboltIP peer can send a multi-frame packet with more frames than MAX_SKB_FRAGS plus one, causing skb_add_rx_frag to write past the fragment array and corrupt adjacent kernel memory. For the CVSS the PR:N is used for the paranoid score because the attacker does not need an account on the victim once a ThunderboltIP link to the target exists. The issue is adjacent-network reachable rather than Internet reachable because it requires access to the Thunderbolt networking link. Impact is at least denial of service via kernel crash and the explicit out-of-bounds write makes privilege escalation or code execution plausible enough for manual review.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Strong Important candidate / Actionable Moderate at minimum (with actual score 7)	YES	NETWORK SKB KPANIC MEMORY PACKET  KPANIC INCREASED_TO_HIGH_BASED_ON_GUESSCVSS DECREASED_TO_MODERATE7_BASED_ON_FALSEPOSCHECKOFKP	NO	NO	checked

======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================

ActionableScore=7
ActionableScoreLower=6

## 1. ActionableScore

* Conservative score: 6
* Paranoid score: 7
* Final recommended bucket: **Strong Important candidate / Actionable Moderate at minimum**::

## 2. Signal breakdown

Triggered signals:

* Remote reachable / network-triggerable: +2
  Triggering is done by a peer over a ThunderboltIP network link. This is adjacent-network exposure, not Internet remote exposure.

* Memory corruption, strong corruption primitive: +2
  The patch explicitly prevents `skb_add_rx_frag()` from writing past `skb_shinfo(skb)->frags[]`. This is an out-of-bounds write in kernel memory.

* Privilege escalation plausible: +1 conservative, +2 paranoid
  Conservative scoring treats this as plausible but not demonstrated LPE because the overwrite target and payload are constrained skb fragment metadata. Paranoid scoring raises this because kernel RX path OOB writes into `skb_shared_info` adjacent memory have historically been high-risk and may be exploitable beyond DoS.

* Reliable kernel crash / strong DoS: +1
  Writing past the skb frags array can corrupt adjacent kernel memory and realistically crash the kernel.

* Confidentiality impact plausible: +1 paranoid
  Not directly demonstrated, but kernel heap corruption may permit disclosure in a worst-case interpretation.

* Integrity impact plausible: +1
  Explicit kernel memory corruption supports integrity impact at least for paranoid/manual-review triage.

Subtracted signals:

* Corruption primitive constrained or metadata-only: -1
  The write is through skb frag descriptors rather than an arbitrary attacker-chosen byte stream.

* Rare / hardware-adjacent exposure: -1
  The attacker needs access to a ThunderboltIP link. This is less exposed than normal TCP/IP networking.

## 3. Reachability analysis

A malicious ThunderboltIP peer can trigger the bug by sending a multi-frame packet with a peer-controlled `frame_count` greater than `MAX_SKB_FRAGS + 1`. No local account on the victim is required once the attacker has access to the Thunderbolt networking link, so PR:N is reasonable for CVSS-style adjacent-network scoring.

This is not broadly Internet reachable. It requires Thunderbolt networking to be active and an attacker-controlled or compromised peer on that link. Containers and namespaces are not the main factor here because the trigger is external packet input on the ThunderboltIP receive path.

Call-site confidence: high. The commit message directly describes the `tbnet_poll()` assembly path and the `skb_add_rx_frag()` call that overruns `skb_shinfo()->frags[]`.

## 4. Severity interpretation

This is stronger than an ordinary Moderate issue because the patch fixes an explicit out-of-bounds write in kernel networking receive code. The realistic impact is at least adjacent-network DoS via memory corruption and likely kernel crash.

Practical privilege escalation is not demonstrated by the patch, and the overwrite is constrained to skb fragment metadata. However, because this is kernel heap memory corruption in an RX path, it should not be auto-closed as a simple DoS. The best practical bucket is Strong Important candidate, with Actionable Moderate as the minimum.

## 5. One-sentence report phrase

A malicious ThunderboltIP peer can send an oversized multi-frame packet that makes `skb_add_rx_frag()` write past `skb_shinfo()->frags[]`, causing adjacent kernel memory corruption with at least crash impact and plausible privilege-escalation concern.

## 6. Manual review recommendation

MANUAL CHECK REQUIRED

Reason: the patch explicitly fixes an skb frags array out-of-bounds write in a network receive path, and although exposure is limited to ThunderboltIP adjacent peers, the memory corruption primitive is serious enough to require manual security review.

======================================================================
UPSTREAM PATCH SUMMARY
======================================================================

Patch: net: thunderbolt: Fix frags[] overflow by bounding frame_count
Commit: 2b3b4e5ff5a58ad32817824b0310e63908b12052
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=2b3b4e5ff5a58ad32817824b0310e63908b12052

Commit description:

tbnet_poll() assembles a multi-frame ThunderboltIP packet into one skb. The
first frame goes into the skb linear area and every further frame is added as
a page fragment.

	skb_add_rx_frag(skb, skb_shinfo(skb)->nr_frags,
			page, hdr_size, frame_size,
			TBNET_RX_PAGE_SIZE - hdr_size);

A packet of frame_count frames therefore ends up with frame_count - 1
fragments. tbnet_check_frame() only bounds the peer supplied frame_count to
TBNET_RING_SIZE / 4 (64), which is far above MAX_SKB_FRAGS (17 by default). A
peer that sends a packet of 19 or more small frames pushes nr_frags past
MAX_SKB_FRAGS, so skb_add_rx_frag() writes past skb_shinfo()->frags[] and
corrupts memory after the shared info.

Tighten the start of packet bound to MAX_SKB_FRAGS + 1 so a packet can never
produce more fragments than frags[] can hold. This matches the recent skb
frags overflow fixes in other receive paths, for example f0813bc ("net:
wwan: t7xx: fix potential skb->frags overflow in RX path") and 600dc40
("net: usb: cdc-phonet: fix skb frags[] overflow in rx_complete()").

Fixes: e69b6c0 ("net: Add support for networking over Thunderbolt cable")
Cc: stable@vger.kernel.org
Signed-off-by: Maoyi Xie <maoyixie.tju@gmail.com>
Acked-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Link: https://patch.msgid.link/178163152194.2486768.14724194232649760778@maoyixie.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Changed files:
  drivers/net/thunderbolt/main.c

Diff excerpt:

Not included in this email. See the upstream URL for the full patch.

Full patch:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=2b3b4e5ff5a58ad32817824b0310e63908b12052

======================================================================
DETAILED REPORT METHODOLOGY
======================================================================

The original Linux kernel CVE announcement for CVE-2026-72157 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72157

The original CVE announcement normally does not include a security-level
estimate. In particular, it may not contain a CVSS assessment, an impact
level, or enough information to determine whether the reported bug is a
practically relevant security issue. One purpose of this parallel CVE list
is to provide that missing technical and prioritization information.

The original goal of the AL-KERNEL project was to prioritize Linux kernel
CVE analysis automatically before manual review. The system can also help
identify non-security issues that may be suitable for automatic closure.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin.

The first analysis stage combines an autonomous classifier with additional
LLM-based analysis. The autonomous classifier runs locally on a CPU and is
based on a backpropagation neural network. Together, these mechanisms
produce a technical vulnerability description, identify likely weakness
types, estimate CVSS severity, and provide input for ActionableScore.

Two CVSS estimates are retained because incomplete kernel vulnerability
information often permits more than one defensible interpretation:

  Conservative CVSS vector: AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H
  The Best / paranoid CVSS vector: AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
  The Best / paranoid CVSS score: 8.8

The conservative vector represents a lower-impact interpretation.
The Best/paranoid vector intentionally represents a plausible upper-bound
interpretation and should not automatically be treated as demonstrated
real-world impact.

CVSS may also need to be adjusted for a particular Linux deployment,
because actual reachability, privileges, enabled kernel configuration,
hardware, namespaces, exposed device nodes, and other environmental
conditions can differ significantly between systems.

A separate ActionableScore mechanism evaluates practical remediation
urgency. Its analysis may include reachability, attack prerequisites,
subsystem exposure, memory-corruption characteristics, denial-of-service
reliability, and possible confidentiality, integrity, or
privilege-escalation impact.

  Conservative ActionableScore: 6
  Paranoid ActionableScore: 7

The final base severity is taken directly from the second tab-separated
field of the AL-KERNEL classification result. ActionableScore does not
replace or independently override that final AL-KERNEL decision, and
if ActionableScore adjusted impact level of ALKERNEL, then you would see
self-readable flags above like INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7.

For an AL-KERNEL result of MODERATE, this report uses the following
additional presentation split:

  ActionableScore below 5   -> MODERATE REGULAR
  ActionableScore 5 or more -> MODERATE 7.0

The distinction between MODERATE REGULAR and MODERATE 7.0 makes it
possible to identify Moderate issues that should receive manual analysis
and fixes before lower-priority MODERATE REGULAR issues. In many cases,
MODERATE REGULAR fixes may wait for a later rebase or routine update.

There is one override in which MODERATE REGULAR becomes MODERATE 7.0
even when the ActionableScore is below 5. When the AL-KERNEL result
contains the KPANIC flag, a MODERATE result is always presented as
MODERATE 7.0. The KPANIC flag selected with few regexps without
usage of AI at all, so it helps to detect cases when Kernel Crash happens
and similar (to filter False-Negative results from the LLM usage).

KPANIC indicates that a reliable kernel crash, kernel panic, or similarly
serious kernel availability impact was identified by the classification
workflow.

AL-KERNEL base severity for this report: MODERATE
KPANIC detected for this report: YES
Published priority for this report (same as in Subject): MODERATE 7.0

These results are intended to support engineering triage. They are
machine-generated estimates, and cases marked for manual review should
be validated by a human security engineer before final disposition.
For more info read docs linked from here: https://kernelcve.org/
(and you can submit you own patch there to generate such a report
for non-existant CVE-id yet).

Note that in many cases this AI tool selects higher severity, than
real is (means you can expect Importants instead of Moderate 7.0 or
Moderates 7.0 instead of regular Moderates). If you see such cases,
please use reply email interface to add additional manual analyses
info to this particular CVE.
And please, please, let me know when you see Lows instead of Importants
or Important instead of Low (because particular for such cases I
need to tune this AI tool to make it better for this one and next similar).
My contact email for such notifications is alexanjelausa@gmail.com (and both
send reply to CVE record itself too and see "reply" button below for howto reply).