Kernel use-after-free via socket-close race
Published Sep 4, 2026 · Updated Sep 4, 2026
Use-after-free in Linux kernel espintcp sockets from 5.6 allows attackers to trigger a stale skb read by racing socket closure. espintcp_close() frees emsg->skb without a socket lock while xfrm_trans_reinject work can pass the same buffer to skb_send_sock_locked(). Reachability requires an espintcp socket-close race with pending reinjection work; the upstream notice does not publish a further consequence.
Summary
What happened
Use-after-free in Linux kernel espintcp sockets from 5.6 allows attackers to trigger a stale skb read by racing socket closure. espintcp_close() frees emsg->skb without a socket lock while xfrm_trans_reinject work can pass the same buffer to skb_send_sock_locked(). Reachability requires an espintcp socket-close race with pending reinjection work; the upstream notice does not publish a further consequence.
The record
- CVE
- CVE-2026-80848
- Published
- Sep 4, 2026
- Updated
- Sep 4, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 4, 2026CVE publishedPublication date reported by the CVE source.
- Sep 4, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.6
- Affected versionversion=e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <24efebecf415ba264adba0f0491cec436463a14f
- Affected versionversion=e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <29121c5e6591da527e8e36ddac7120dc527f574d
- Affected versionversion=e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <4b31a875693c480c611519faca46216514e3e052
- Affected versionversion=e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <4bc0dfa28dca6fc0084203732695968049c44072
- Affected versionversion=e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <54b41ad14da9a981131ab6e4d3f79321a503ea5d
- Affected versionversion=e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <deb232e884877bf10b4ce2580909eedec986c284
- Affected versionversion=e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <eb3bbf29c723fe75c0eb92be14f0ec92971fe272
- Affected versionversion=e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <ed5d9102190c45fc70121c036b0626b740040b75
- Affected versionversion=e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 <ff8dd7a932f34409a56e1b91a1219340f17457e9
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo