Kernel crash via failed CXL device registration
Published Oct 4, 2025 · Updated Oct 4, 2025
A NULL pointer dereference in Linux kernel CXL guest registration allows local users to crash the kernel after device registration fails. The cxl_register_afu() and cxl_register_adapter() error paths call device_unregister() for a device that device_register() never added, causing removal of an unregistered device. Reachability requires a registration failure during CXL guest AFU or adapter initialization; public sources do not identify how local users induce that failure.
Summary
What happened
A NULL pointer dereference in Linux kernel CXL guest registration allows local users to crash the kernel after device registration fails. The cxl_register_afu() and cxl_register_adapter() error paths call device_unregister() for a device that device_register() never added, causing removal of an unregistered device. Reachability requires a registration failure during CXL guest AFU or adapter initialization; public sources do not identify how local users induce that failure.
The record
- CVE
- CVE-2022-50481
- Published
- Oct 4, 2025
- Updated
- Oct 4, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 4, 2025CVE publishedPublication date reported by the CVE source.
- Oct 4, 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=14baf4d9c739e6e69150512d2eb23c71fffcc192 <170e8c2d2b61e15e7f7cfeded81bc1e959a15ed8
- Affected versionversion=14baf4d9c739e6e69150512d2eb23c71fffcc192 <1ae581696b7a799afa39a664c4b721569643f58a
- Affected versionversion=14baf4d9c739e6e69150512d2eb23c71fffcc192 <60b2ed21a65f3f5318666ccd765c3507991370cf
- Affected versionversion=14baf4d9c739e6e69150512d2eb23c71fffcc192 <61c80d1c3833e196256fb060382db94f24d3d9a7
- Affected versionversion=14baf4d9c739e6e69150512d2eb23c71fffcc192 <96fba6fb95bdede80583c262ac185da09661f264
- Affected versionversion=14baf4d9c739e6e69150512d2eb23c71fffcc192 <ab44c182353be101c3be9465e1d15d42130c53c4
- Affected versionversion=14baf4d9c739e6e69150512d2eb23c71fffcc192 <b32559ee4e6667c5c3daf4ec5454c277d1f255d2
- Affected versionversion=14baf4d9c739e6e69150512d2eb23c71fffcc192 <d775a1da5a52b4f4bb02f2707ba420d1bec48dbb
- Affected versionversion=14baf4d9c739e6e69150512d2eb23c71fffcc192 <e5021bbf11b024cc65ea1e84c377df484183be4b
- Affected versionversion=4.6
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