Local kernel crash via KCM socket race
Published Oct 16, 2022 · Updated Apr 15, 2025
Race condition in Linux Kernel before 5.19 allows local users to crash the kernel via concurrent release of KCM sockets. The kcm_tx_work worker can access sk_socket after kcm_release concurrently orphaned the socket, producing a NULL-pointer dereference. Reaching the fault requires local access to create and release KCM sockets; the documented consequence is kernel service interruption, not data disclosure or code execution.
Summary
What happened
Race condition in Linux Kernel before 5.19 allows local users to crash the kernel via concurrent release of KCM sockets. The kcm_tx_work worker can access sk_socket after kcm_release concurrently orphaned the socket, producing a NULL-pointer dereference. Reaching the fault requires local access to create and release KCM sockets; the documented consequence is kernel service interruption, not data disclosure or code execution.
The record
- CVE
- CVE-2022-3521
- Published
- Oct 16, 2022
- Updated
- Apr 15, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-362, T1499.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 16, 2022CVE publishedPublication date reported by the CVE source.
- Apr 15, 2025Record 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=n/a
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