Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 9 days later

    Published

  3. · 45 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.19% · top 91% of all CVEs (15 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 – < 239d0f71af09dc2029fd4d730cb24b8c83aaa43a
    • affected e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 – < f00235f9d12301183d61f75fbe4105506f3e5140
    • affected e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 – < 6af5cdb03819a5ce6e945992635c6c5e91045367
    • affected e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 – < 2dd1609cadff46c4b20ce53b91ab9cce1380456a
    • affected e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 – < c296d25efbc840be24de83f56d43bc47e714ace9
    • affected e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 – < 328e40aa774b446969c69b654c52a051a95af8a1
    • affected e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 – < 7911e0236616487b89db6bd3ba3f408abd10eb23
    • affected e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 – < 943d95233b8b4a88994e244fcf466f8c403d63f1
    • affected e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 – < e1d7c5ac1c246ce5775f604515de0a59fbf2116e
  • Linux · Linux

    • affected 5.6
    • unaffected < 5.6
    • unaffected 5.10.269 – ≤ 5.10.*
    • unaffected 5.15.220 – ≤ 5.15.*
    • unaffected 6.1.187 – ≤ 6.1.*
    • unaffected 6.6.156 – ≤ 6.6.*
    • unaffected 6.12.108 – ≤ 6.12.*
    • unaffected 6.18.49 – ≤ 6.18.*
    • unaffected 7.1.13 – ≤ 7.1.*
    • unaffected 7.2.3 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References9

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-80846 badge
[![CVE-2026-80846](https://cveledger.app/badge/CVE-2026-80846.svg)](https://cveledger.app/cve/CVE-2026-80846)

Record last updated .