Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-80846: xfrm: drop ESP-in-TCP packets with no ingress device

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
  • Fixed version: Linux Linux 239d0f71af09dc2029fd4d730cb24b8c83aaa43a, 2dd1609cadff46c4b20ce53b91ab9cce1380456a, 328e40aa774b446969c69b654c52a051a95af8a1.

Low priority for now. Upgrade to Linux Linux 239d0f71af09dc2029fd4d730cb24b8c83aaa43a, 2dd1609cadff46c4b20ce53b91ab9cce1380456a, 328e40aa774b446969c69b654c52a051a95af8a1 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: xfrm: drop ESP-in-TCP packets with no ingress device ESP-in-TCP receives records through the TCP strparser. handle_esp() restores skb->dev from the saved skb_iif before passing the packet into the XFRM input path. Queued TCP data can be processed after the original ingress device has been removed, for example during veth or net namespace teardown. In that case dev_get_by_index_rcu() returns NULL. The XFRM IPv4 and IPv6 input paths both expect skb->dev to be valid while building the route lookup, so queued ESP-in-TCP data can dereference a NULL device. Drop the packet if the saved ingress device can no longer be resolved. Such a packet can no longer be routed through the normal XFRM receive path, and this preserves the existing behaviour for packets whose ingress device still exists.

—No exploit Fix available
Published
Sep 4, 2026
Updated
Oct 19, 2026
EPSS
0.1% · 9th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

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

Follow CVE-2026-80846

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

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack 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 (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

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

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

    • 5.6affected
    • e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and later · before 239d0f71af09dc2029fd4d730cb24b8c83aaa43aaffected · git
    • e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and later · before f00235f9d12301183d61f75fbe4105506f3e5140affected · git
    • e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and later · before 6af5cdb03819a5ce6e945992635c6c5e91045367affected · git
    • e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and later · before 2dd1609cadff46c4b20ce53b91ab9cce1380456aaffected · git
    • e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and later · before c296d25efbc840be24de83f56d43bc47e714ace9affected · git
    • e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and later · before 328e40aa774b446969c69b654c52a051a95af8a1affected · git
    • e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and later · before 7911e0236616487b89db6bd3ba3f408abd10eb23affected · git
    • e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and later · before 943d95233b8b4a88994e244fcf466f8c403d63f1affected · git
    • e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and later · before e1d7c5ac1c246ce5775f604515de0a59fbf2116eaffected · git

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.187-16.1.187-1
Debian:12linux-6.12before 6.12.111-1~deb12u16.12.111-1~deb12u1
Debian:13linuxbefore 6.12.111-16.12.111-1
Debian:14linuxbefore 7.1.13-17.1.13-1

Same product

linux: all records

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-80844Sep 4, 2026 · xfrm: ah6: validate routing header segments_left
    0Monitor
  • ← EarlierCVE-2026-80845Sep 4, 2026 · xfrm: avoid lock inversion in nat keepalive work
    0Monitor
  • Later →CVE-2026-80847Sep 4, 2026 · tcp: clamp route advmss to TCP_MIN_MSS
    0Monitor

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 Linux239d0f71af09dc2029fd4d730cb24b8c83aaa43aVendor (CNA)
Linux Linux2dd1609cadff46c4b20ce53b91ab9cce1380456aVendor (CNA)
Linux Linux328e40aa774b446969c69b654c52a051a95af8a1Vendor (CNA)
Linux Linux6af5cdb03819a5ce6e945992635c6c5e91045367Vendor (CNA)
Linux Linux7911e0236616487b89db6bd3ba3f408abd10eb23Vendor (CNA)
Linux Linux943d95233b8b4a88994e244fcf466f8c403d63f1Vendor (CNA)
Linux Linuxc296d25efbc840be24de83f56d43bc47e714ace9Vendor (CNA)
Linux Linuxe1d7c5ac1c246ce5775f604515de0a59fbf2116eVendor (CNA)
Linux Linuxf00235f9d12301183d61f75fbe4105506f3e5140Vendor (CNA)
azl3 kernel 6.6.150.1-1 on Azure Linux 3.0—Microsoft (MSRC)
debian:linux6.1.187-1 · Debian:12Package registry (OSV)
debian:linux-6.126.12.111-1~deb12u1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

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.

No dated events beyond publication.

EPSS, last 120 days

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

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

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.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (8 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records