Kernel memory corruption via premature device release
Published Apr 24, 2026 · Updated Apr 24, 2026
Use-after-free in the XFRM subsystem in affected Linux kernels allows local users to crash the kernel or corrupt kernel memory. After asynchronous crypto completion, xfrm_input_resume() drops the skb device reference before NF_HOOK and its callback finish using skb->dev, allowing device teardown to race with later access. An unprivileged local user must create user and network namespaces, configure transport-mode XFRM state, inject traffic, and race device teardown; exploitation can also expose kernel memory.
Summary
What happened
Use-after-free in the XFRM subsystem in affected Linux kernels allows local users to crash the kernel or corrupt kernel memory. After asynchronous crypto completion, xfrm_input_resume() drops the skb device reference before NF_HOOK and its callback finish using skb->dev, allowing device teardown to race with later access. An unprivileged local user must create user and network namespaces, configure transport-mode XFRM state, inject traffic, and race device teardown; exploitation can also expose kernel memory.
The record
- CVE
- CVE-2026-31663
- Published
- Apr 24, 2026
- Updated
- Apr 24, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-826, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 24, 2026CVE publishedPublication date reported by the CVE source.
- Apr 24, 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=4.15
- Affected versionversion=69895c5ea0ca2e8d7de1e6d36965d0ab9730787f
- Affected versionversion=833760100588acfb267dac4d6a02ab9931237739
- Affected versionversion=acf568ee859f098279eadf551612f103afdacb4e <0f451b43c88bf2b9c038b414be580efee42e031b
- Affected versionversion=acf568ee859f098279eadf551612f103afdacb4e <1c428b03840094410c5fb6a5db30640486bbbfcb
- Affected versionversion=acf568ee859f098279eadf551612f103afdacb4e <5002beda5cac69d522dc54da0d5d463ed9c963d2
- Affected versionversion=e095ecaec6d94aa2156cceb98a85d409b51190f3
What conditions does exploitation require?
What is affected?
Published CVSS scores
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
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