Remote kernel crash via SMC listener race
Published Apr 3, 2026 · Updated Apr 3, 2026
Use-after-free in the Linux Kernel SMC TCP receive path allows remote attackers to crash the kernel through an exposed SMC listener. The callback reads sk_user_data without RCU protection or a live smc_sock reference while concurrent close clears the pointer and frees the object. An enabled SMC listening socket and concurrent handshake traffic plus listener teardown are required; the demonstrated consequence is an oops or panic.
Summary
What happened
Use-after-free in the Linux Kernel SMC TCP receive path allows remote attackers to crash the kernel through an exposed SMC listener. The callback reads sk_user_data without RCU protection or a live smc_sock reference while concurrent close clears the pointer and frees the object. An enabled SMC listening socket and concurrent handshake traffic plus listener teardown are required; the demonstrated consequence is an oops or panic.
The record
- CVE
- CVE-2026-23450
- Published
- Apr 3, 2026
- Updated
- Apr 3, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-416, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 3, 2026CVE publishedPublication date reported by the CVE source.
- Apr 3, 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.18
- Affected versionversion=8270d9c21041470f58348248b9d9dcf3bf79592e <1e4f873879e075bbd4eb1c644d6933303ac5eba4
- Affected versionversion=8270d9c21041470f58348248b9d9dcf3bf79592e <1fab5ece76fb42a761178dcd0ebcbf578377b0dd
- Affected versionversion=8270d9c21041470f58348248b9d9dcf3bf79592e <6d5e4538364b9ceb1ac2941a4deb86650afb3538
- Affected versionversion=8270d9c21041470f58348248b9d9dcf3bf79592e <cadf3da46c15523fba90d80c9955f536ee3b4023
- Affected versionversion=8270d9c21041470f58348248b9d9dcf3bf79592e <f00fc26c8a06442b225a350fe000c0a11483e6a3
- Affected versionversion=8270d9c21041470f58348248b9d9dcf3bf79592e <fd7579f0a2c84ba8a7d4f206201b50dc8ddf90c2
- Affected versionversion=ebfee3e153f67c8b38eb94a7062ee94aa6f92708
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
- Syzkaller smc_tcp_syn_recv_sock crash reproducerproof of concept · validated
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