CVE-2026-80848

xfrm: espintcp: fix UAF during close

N/A
Published: September 4, 2026 at 03:54 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
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

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

5.6e27cca96cd68fa2c6814c90f9a1cfd36bb68c593
Vendor states this is fixed in 24efebecf415ba264adba0f0491cec436463a14f (fixed)
Vendor states this is fixed in 29121c5e6591da527e8e36ddac7120dc527f574d (fixed)
Vendor states this is fixed in 4b31a875693c480c611519faca46216514e3e052 (fixed)
Vendor states this is fixed in 4bc0dfa28dca6fc0084203732695968049c44072 (fixed)
Vendor states this is fixed in 54b41ad14da9a981131ab6e4d3f79321a503ea5d (fixed)
Vendor states this is fixed in deb232e884877bf10b4ce2580909eedec986c284 (fixed)
Vendor states this is fixed in eb3bbf29c723fe75c0eb92be14f0ec92971fe272 (fixed)
Vendor states this is fixed in ed5d9102190c45fc70121c036b0626b740040b75 (fixed)
Vendor states this is fixed in ff8dd7a932f34409a56e1b91a1219340f17457e9 (fixed)
Vendor states this is fixed in 5.10.269 (unaffected)
Vendor states this is fixed in 5.15.220 (unaffected)
Vendor states this is fixed in 5.6 (unaffected)
Vendor states this is fixed in 6.1.187 (unaffected)
Vendor states this is fixed in 6.12.108 (unaffected)
Vendor states this is fixed in 6.18.49 (unaffected)
Vendor states this is fixed in 6.6.156 (unaffected)
Vendor states this is fixed in 7.1.13 (unaffected)
Vendor states this is fixed in 7.2.3 (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.

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