Kernel crash via invalid device unregistration
Published Sep 15, 2025 · Updated Sep 15, 2025
NULL pointer dereference in affected Linux kernel releases allows local users to crash the kernel during CXL PCI accelerator initialization. When device_register() fails in cxl_pci_init_afu() or cxl_pci_init_adapter(), the error path calls device_unregister() for a device that was never added. Exploitation requires POWER8 or POWER9 CAPI accelerator hardware and a device-registration failure; the published consequence is a kernel crash.
Summary
What happened
NULL pointer dereference in affected Linux kernel releases allows local users to crash the kernel during CXL PCI accelerator initialization. When device_register() fails in cxl_pci_init_afu() or cxl_pci_init_adapter(), the error path calls device_unregister() for a device that was never added. Exploitation requires POWER8 or POWER9 CAPI accelerator hardware and a device-registration failure; the published consequence is a kernel crash.
The record
- CVE
- CVE-2022-50244
- Published
- Sep 15, 2025
- Updated
- Sep 15, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499.004
- 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=3.18
- Affected versionversion=f204e0b8cedd7da1dfcfd05ed6b7692737e24029 <02cd3032b154fa02fdf90e7467abaeed889330b2
- Affected versionversion=f204e0b8cedd7da1dfcfd05ed6b7692737e24029 <0f63c0ddc2ea20d783d29243f4dbe0f9e95dfdec
- Affected versionversion=f204e0b8cedd7da1dfcfd05ed6b7692737e24029 <139abd4c626a6f7ce02789ed5f73aa2256e0542b
- Affected versionversion=f204e0b8cedd7da1dfcfd05ed6b7692737e24029 <22511eefa61db26e12c97dd7ada3071dbdfcb004
- Affected versionversion=f204e0b8cedd7da1dfcfd05ed6b7692737e24029 <2f5fd31b2f24b9b8a80ab566fd8c4e1e94cb4339
- Affected versionversion=f204e0b8cedd7da1dfcfd05ed6b7692737e24029 <361412dae1690d4b5df6f92fc943cdc773c95cbc
- Affected versionversion=f204e0b8cedd7da1dfcfd05ed6b7692737e24029 <82e5481428faf11c79b9c094dd24a1849bbf64ac
- Affected versionversion=f204e0b8cedd7da1dfcfd05ed6b7692737e24029 <82e68432668ae75b4c814d160f6987ecb0681273
- Affected versionversion=f204e0b8cedd7da1dfcfd05ed6b7692737e24029 <c4b2e35df919d99bbbed033c2fa0b607f9f463b5
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