CVE-2022-50481
BaseFortify
Publication date: 2025-10-04
Last updated on: 2026-01-23
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 4.6 (inc) to 4.9.337 (exc) |
| linux | linux_kernel | From 4.10 (inc) to 4.14.303 (exc) |
| linux | linux_kernel | From 4.15 (inc) to 4.19.270 (exc) |
| linux | linux_kernel | From 4.20 (inc) to 5.4.229 (exc) |
| linux | linux_kernel | From 5.5 (inc) to 5.10.163 (exc) |
| linux | linux_kernel | From 5.11 (inc) to 5.15.86 (exc) |
| linux | linux_kernel | From 5.16 (inc) to 6.0.16 (exc) |
| linux | linux_kernel | From 6.1 (inc) to 6.1.2 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-476 | The product dereferences a pointer that it expects to be valid but is NULL. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a possible null pointer dereference in the Linux kernel's cxl_guest_init_afu|adapter() function. It occurs when device_register() fails in cxl_register_afu|adapter(), causing the device not to be added. If device_unregister() is called in this error path, it leads to a null pointer dereference because it tries to remove a device that was never added. The fix involves properly handling the error by splitting device_unregister() into device_del() and put_device(), and using put_device() to release the reference when registration fails.
How can this vulnerability impact me? :
This vulnerability can cause a null pointer dereference in the Linux kernel, which may lead to a kernel crash or system instability. Such crashes can result in denial of service or unexpected behavior of the system.