CVE-2026-80848
xfrm: espintcp: fix UAF during close
Reported by linux · Published September 4, 2026
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.
EPSS 0.19% · 9.2th percentile
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| Linux | Linux | ff8dd7a932f34409a56e1b91a1219340f17457e9, ed5d9102190c45fc70121c036b0626b740040b75, eb3bbf29c723fe75c0eb92be14f0ec92971fe272, deb232e884877bf10b4ce2580909eedec986c284, 54b41ad14da9a981131ab6e4d3f79321a503ea5d, 4bc0dfa28dca6fc0084203732695968049c44072, 4b31a875693c480c611519faca46216514e3e052, 29121c5e6591da527e8e36ddac7120dc527f574d, 24efebecf415ba264adba0f0491cec436463a14f |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | e27cca96cd68fa2c6814c90f9a1cfd36bb68c593, e27cca96cd68fa2c6814c90f9a1cfd36bb68c593, e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 |
| Linux | Linux | 5.6, 0, 5.10.269 |
| Linux | Linux | 7.3, 0, 5.10.269 |
| linux | linux_kernel | 5.6, 5.6, 5.6 |
Timeline
- Sep 4, 2026 Coalition ESS Score
- Sep 4, 2026 CVE Published
- Sep 5, 2026 EPSS Score (14 in total, the first dated here)
- Oct 19, 2026 CVE Updated
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2026-80848
vulnetix vdb fixes CVE-2026-80848
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-80848/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart