CVE-2026-72157

net: thunderbolt: Fix frags[] overflow by bounding frame_count

HIGH
8.8
CVSS Score
Published: August 15, 2026 at 05:53 AM UTC
Updated: October 16, 2026 at 07:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.8
Exploit prediction
EPSS 0.4%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: net: thunderbolt: Fix frags[] overflow by bounding frame_count 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 f0813bcd2d9d ("net: wwan: t7xx: fix potential skb->frags overflow in RX path") and 600dc40554dc ("net: usb: cdc-phonet: fix skb frags[] overflow in rx_complete()").

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.15e69b6c02b4c3b8d03be7136f90dd9551ad5a5a5e
Vendor states this is fixed in 2b3b4e5ff5a58ad32817824b0310e63908b12052 (fixed)
Vendor states this is fixed in 55d9895f89970501fe126d1026b586b04a224c27 (fixed)
Vendor states this is fixed in 569ba39b2d12995a29dc158e5b4de6e449278f30 (fixed)
Vendor states this is fixed in 6262f51e09d8dc8b07599a9e4f03bd3989d13fff (fixed)
Vendor states this is fixed in e27beb4536cbf1d59e2d8c2840e87d972aba906f (fixed)
Vendor states this is fixed in e5824d5b841d99a2bcdd4e2c256643293bbc22c1 (fixed)
Vendor states this is fixed in f96b3b35c622d565eff2438993e028d280163f5c (fixed)
Vendor states this is fixed in fe6b606fbf0c3beb94ccf17fcf31d8c2138264e3 (fixed)
Vendor states this is fixed in 4.15 (unaffected)
Vendor states this is fixed in 5.10.266 (unaffected)
Vendor states this is fixed in 5.15.217 (unaffected)
Vendor states this is fixed in 6.1.184 (unaffected)
Vendor states this is fixed in 6.12.97 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.8HIGHLinux
Vector?

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card