CVE-2022-50218
BaseFortify
Publication date: 2025-06-18
Last updated on: 2025-11-19
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
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 related to the Linux kernel driver for the isl29028 light sensor. The issue arises because the driver uses a non-managed form of the register function inconsistently between the probe and remove functions. Specifically, in the isl29028_remove() function, the non-managed form is used, but it was not used in the probe function, which can cause improper release order. This mismatch can lead to a general protection fault and a null pointer dereference, causing kernel crashes or instability.
How can this vulnerability impact me? :
This vulnerability can cause the Linux kernel to crash or become unstable due to a general protection fault and null pointer dereference when the isl29028 driver is removed. This can lead to system instability, potential denial of service, or unexpected behavior on systems using this driver.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring the system logs for specific kernel warning messages related to the isl29028 driver removal. Look for log entries similar to: '[ 32.374955] isl29028 0-0010: remove' followed by 'general protection fault' and 'KASAN: null-ptr-deref' errors. You can use commands like 'dmesg | grep isl29028' or 'journalctl -k | grep isl29028' to find these messages in the kernel logs.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves updating the Linux kernel to a version where the isl29028 driver uses the managed form of the register function consistently in both probe and remove functions, as the fix addresses the release order issue causing the fault. Until an update is applied, monitoring logs for the fault and avoiding operations that trigger the isl29028_remove() function may reduce risk.