CVE-2026-81000

net: tun: bound receive headroom

HIGH
7.8
CVSS Score
Published: September 11, 2026 at 07:42 PM UTC
Updated: October 19, 2026 at 09:17 AM 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
HIGH7.8
Exploit prediction
EPSS 0.4%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: net: tun: bound receive headroom tun_get_user() uses tun->align both as skb headroom and when choosing how much packet data to keep linear. OVS can propagate an oversized headroom request from another port to TUN or TAP. When align is larger than the usable space in a one-page skb head, SKB_MAX_HEAD(align) underflows and the result becomes negative when stored in good_linear. That value later wraps when assigned to the size_t linear variable, and tun_alloc_skb() can place skb->data outside the allocated head. Bound the headroom stored by TUN to the one-page skb-head budget and the largest non-sentinel 16-bit skb header offset. Leave one linear byte for raw TUN and a complete Ethernet header for TAP, including NET_IP_ALIGN. Also pull the raw-TUN protocol byte and the TAP Ethernet header before accessing them, so these checks remain safe for nonlinear skbs supplied by other allocation paths.

Affected

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

4.6eaea34b23c46bf17b4a5638be69ab3561854f34b
Vendor states this is fixed in 010eee265d6bd8769b6a523d2a0693d9b3f5df43 (fixed)
Vendor states this is fixed in 0ada54ea63e48b9c1608e917ccb7dfadbe86db28 (fixed)
Vendor states this is fixed in 18ef24cdb2eba32e38f1d27f2d02b7b4212e8f76 (fixed)
Vendor states this is fixed in 379d85c7f25f3e05a428225e6b8a65613c6e9b9d (fixed)
Vendor states this is fixed in 447c9303942c439a117d9b76ce6d6e2116b38ee7 (fixed)
Vendor states this is fixed in 708e87937de93f445225c134a2e20519f9b4ce60 (fixed)
Vendor states this is fixed in ad715e713610d2d5473c3a6498c825ccecf26491 (fixed)
Vendor states this is fixed in e098d9cc8859614a7f7baebc96e32a5a16b18ed2 (fixed)
Vendor states this is fixed in 4.6 (unaffected)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.109 (unaffected)
Vendor states this is fixed in 6.18.50 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.4 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (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

7.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