Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-81000: net: tun: bound receive headroom

HighCVSS 7.8 · v3.1—Proof of concept Fix available

Noroxi assessment

Priority: Monitor (action score 31/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.35% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 010eee265d6bd8769b6a523d2a0693d9b3f5df43, 0ada54ea63e48b9c1608e917ccb7dfadbe86db28, 18ef24cdb2eba32e38f1d27f2d02b7b4212e8f76.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 010eee265d6bd8769b6a523d2a0693d9b3f5df43, 0ada54ea63e48b9c1608e917ccb7dfadbe86db28, 18ef24cdb2eba32e38f1d27f2d02b7b4212e8f76 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
Sep 11, 2026
Updated
Oct 19, 2026
EPSS
0.3% · 29th percentile
CWE
—

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
7.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-81000

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.6affected
    • eaea34b23c46bf17b4a5638be69ab3561854f34b and later · before ad715e713610d2d5473c3a6498c825ccecf26491affected · git
    • eaea34b23c46bf17b4a5638be69ab3561854f34b and later · before 708e87937de93f445225c134a2e20519f9b4ce60affected · git
    • eaea34b23c46bf17b4a5638be69ab3561854f34b and later · before 18ef24cdb2eba32e38f1d27f2d02b7b4212e8f76affected · git
    • eaea34b23c46bf17b4a5638be69ab3561854f34b and later · before 010eee265d6bd8769b6a523d2a0693d9b3f5df43affected · git
    • eaea34b23c46bf17b4a5638be69ab3561854f34b and later · before 379d85c7f25f3e05a428225e6b8a65613c6e9b9daffected · git
    • eaea34b23c46bf17b4a5638be69ab3561854f34b and later · before e098d9cc8859614a7f7baebc96e32a5a16b18ed2affected · git
    • eaea34b23c46bf17b4a5638be69ab3561854f34b and later · before 0ada54ea63e48b9c1608e917ccb7dfadbe86db28affected · git
    • eaea34b23c46bf17b4a5638be69ab3561854f34b and later · before 447c9303942c439a117d9b76ce6d6e2116b38ee7affected · git
    • before 4.6not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.59.1.el10_26.12.0-211.59.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.59.1.el10_26.12.0-211.59.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.59.1.el10_26.12.0-211.59.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.59.1.el10_26.12.0-211.59.1.el10_2
AlmaLinux:10kernel-debug-develbefore 6.12.0-211.59.1.el10_26.12.0-211.59.1.el10_2
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-211.59.1.el10_26.12.0-211.59.1.el10_2
AlmaLinux:10kernel-develbefore 6.12.0-211.59.1.el10_26.12.0-211.59.1.el10_2
AlmaLinux:10kernel-devel-matchedbefore 6.12.0-211.59.1.el10_26.12.0-211.59.1.el10_2
AlmaLinux:10kernel-docbefore 6.12.0-211.59.1.el10_26.12.0-211.59.1.el10_2
AlmaLinux:10kernel-headersbefore 6.12.0-211.59.1.el10_26.12.0-211.59.1.el10_2
AlmaLinux:10kernel-zfcpdump-develbefore 6.12.0-211.59.1.el10_26.12.0-211.59.1.el10_2
AlmaLinux:10kernel-zfcpdump-devel-matchedbefore 6.12.0-211.59.1.el10_26.12.0-211.59.1.el10_2
AlmaLinux:10perfbefore 6.12.0-211.59.1.el10_26.12.0-211.59.1.el10_2
AlmaLinux:10python3-perfbefore 6.12.0-211.59.1.el10_26.12.0-211.59.1.el10_2
AlmaLinux:8bpftoolbefore 4.18.0-553.167.1.el8_104.18.0-553.167.1.el8_10
AlmaLinux:8kernelbefore 4.18.0-553.167.1.el8_104.18.0-553.167.1.el8_10
AlmaLinux:8kernel-abi-stablelistsbefore 4.18.0-553.167.1.el8_104.18.0-553.167.1.el8_10
AlmaLinux:8kernel-corebefore 4.18.0-553.167.1.el8_104.18.0-553.167.1.el8_10
AlmaLinux:8kernel-cross-headersbefore 4.18.0-553.167.1.el8_104.18.0-553.167.1.el8_10
AlmaLinux:8kernel-debugbefore 4.18.0-553.167.1.el8_104.18.0-553.167.1.el8_10
AlmaLinux:8kernel-debug-corebefore 4.18.0-553.167.1.el8_104.18.0-553.167.1.el8_10
AlmaLinux:8kernel-debug-develbefore 4.18.0-553.167.1.el8_104.18.0-553.167.1.el8_10
AlmaLinux:8kernel-debug-modulesbefore 4.18.0-553.167.1.el8_104.18.0-553.167.1.el8_10
AlmaLinux:8kernel-debug-modules-extrabefore 4.18.0-553.167.1.el8_104.18.0-553.167.1.el8_10

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-80998Sep 11, 2026 · net: bnxt: ring the doorbell when SW USO exits early
    30Monitor
  • ← EarlierCVE-2026-80999Sep 11, 2026 · net: dsa: realtek: use gpiod_set_value_cansleep for reset GPIO
    0Monitor
  • Later →CVE-2026-81001Sep 11, 2026 · slip: fix use-after-free in sl_sync()
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux010eee265d6bd8769b6a523d2a0693d9b3f5df43Vendor (CNA)
Linux Linux0ada54ea63e48b9c1608e917ccb7dfadbe86db28Vendor (CNA)
Linux Linux18ef24cdb2eba32e38f1d27f2d02b7b4212e8f76Vendor (CNA)
Linux Linux379d85c7f25f3e05a428225e6b8a65613c6e9b9dVendor (CNA)
Linux Linux447c9303942c439a117d9b76ce6d6e2116b38ee7Vendor (CNA)
Linux Linux708e87937de93f445225c134a2e20519f9b4ce60Vendor (CNA)
Linux Linuxad715e713610d2d5473c3a6498c825ccecf26491Vendor (CNA)
Linux Linuxe098d9cc8859614a7f7baebc96e32a5a16b18ed2Vendor (CNA)
almalinux:bpftool4.18.0-553.167.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel4.18.0-553.167.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt4.18.0-553.167.1.rt7.508.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-core4.18.0-553.167.1.rt7.508.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug4.18.0-553.167.1.rt7.508.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-core4.18.0-553.167.1.rt7.508.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-devel4.18.0-553.167.1.rt7.508.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-modules4.18.0-553.167.1.rt7.508.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-modules-extra4.18.0-553.167.1.rt7.508.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-devel4.18.0-553.167.1.rt7.508.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-modules4.18.0-553.167.1.rt7.508.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-modules-extra4.18.0-553.167.1.rt7.508.el8_10 · AlmaLinux:8Package registry (OSV)
debian:linux6.1.190-1 · Debian:12Package registry (OSV)
debian:linux6.12.111-1 · Debian:13Package registry (OSV)
debian:linux-6.126.12.111-1~deb12u1 · Debian:12Package registry (OSV)
red hat:kernel-rt0:4.18.0-553.167.1.rt7.508.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-core0:4.18.0-553.167.1.rt7.508.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug0:4.18.0-553.167.1.rt7.508.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-core0:4.18.0-553.167.1.rt7.508.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-debuginfo0:4.18.0-553.167.1.rt7.508.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-devel0:4.18.0-553.167.1.rt7.508.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-kvm0:4.18.0-553.167.1.rt7.508.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)

+6

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×3

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHub3 repositories2026-09-18 → 2026-09-21

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. First PoC+6 d
  3. TodayNov 16, 2026+65 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

All records