Local availability loss via KCM data race
Published Sep 15, 2025 · Updated Sep 15, 2025
A data race in the Linux kernel KCM subsystem allows local users to cause loss of system availability through concurrent socket activity. The kcm_rfree function reads kcm->rx_psock without synchronization while unreserve_rx_kcm can concurrently replace that pointer with NULL, leaving the receive/free path with an inconsistent value. Low-privileged local access and use of the KCM socket path are required; public records do not specify whether availability loss manifests as a hang or crash.
Summary
What happened
A data race in the Linux kernel KCM subsystem allows local users to cause loss of system availability through concurrent socket activity. The kcm_rfree function reads kcm->rx_psock without synchronization while unreserve_rx_kcm can concurrently replace that pointer with NULL, leaving the receive/free path with an inconsistent value. Low-privileged local access and use of the KCM socket path are required; public records do not specify whether availability loss manifests as a hang or crash.
The record
- CVE
- CVE-2022-50291
- Published
- Sep 15, 2025
- Updated
- Sep 15, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 15, 2025CVE publishedPublication date reported by the CVE source.
- Sep 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=4.6
- Affected versionversion=ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 <12a0eb340c9a22e0f8c00d2c0c1a60695ead926a
- Affected versionversion=ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 <13dba69e18d04c8eec7596369f2a0596b0260275
- Affected versionversion=ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 <15e4dabda11b0fa31d510a915d1a580f47dfc92e
- Affected versionversion=ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 <1b8a5692ab25db4ef1c2cc8e5d21f7a65dc3d079
- Affected versionversion=ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 <342d918cf9a45df9cf11bbe7162b851adefd178f
- Affected versionversion=ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 <bf46af730e58d340f6f740bc69a07c5f6b85c655
- Affected versionversion=ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 <c325f92d8d9b223d5842609ca067e898e9d34566
- Affected versionversion=ab7ac4eb9832e32a09f4e8042705484d2fb0aad3 <e94395e916b48a5b912a0a04570981b5b091acb0
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