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-80848xfrm: espintcp: fix UAF during close

Description

In the Linux kernel, the following vulnerability has been resolved: xfrm: espintcp: fix UAF during close ZDI reported and analyzed a race condition during close for espintcp sockets: espintcp_close() frees emsg->skb via kfree_skb() without holding any socket lock. Concurrently, the xfrm_trans_reinject work queue invokes esp_output_tcp_finish() -> espintcp_push_skb() -> espintcp_push_msgs() -> skb_send_sock_locked(), which reads the same skb as a data source. Fix this by adding a synchronize_rcu() call after resetting sk_prot, since esp_output_tcp_finish() runs under RCU and won't use a socket with sk_prot == &tcp_prot. Simply taking the socket lock in espintcp_close() could lead to leaks, if esp_output_tcp_finish() re-adds an skb in the slot we just freed. After this, the existing barrier() is no longer needed.

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 – < 29121c5e6591da527e8e36ddac7120dc527f574d
    • affected e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 – < ed5d9102190c45fc70121c036b0626b740040b75
    • affected e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 – < 4bc0dfa28dca6fc0084203732695968049c44072
    • affected e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 – < ff8dd7a932f34409a56e1b91a1219340f17457e9
    • affected e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 – < 4b31a875693c480c611519faca46216514e3e052
    • affected e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 – < 24efebecf415ba264adba0f0491cec436463a14f
    • affected e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 – < eb3bbf29c723fe75c0eb92be14f0ec92971fe272
    • affected e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 – < 54b41ad14da9a981131ab6e4d3f79321a503ea5d
    • affected e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 – < deb232e884877bf10b4ce2580909eedec986c284
  • 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-80848 badge
[![CVE-2026-80848](https://cveledger.app/badge/CVE-2026-80848.svg)](https://cveledger.app/cve/CVE-2026-80848)

Record last updated .