CVE-2022-50381
BaseFortify
Publication date: 2025-09-18
Last updated on: 2025-12-11
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 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.87 (exc) |
| linux | linux_kernel | From 5.16 (inc) to 6.0.17 (exc) |
| linux | linux_kernel | From 6.1 (inc) to 6.1.3 (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 crash in the Linux kernel's mempool_free function caused by a race condition during the freeing of a bio structure. Specifically, the crash happens when bio_put is called after the bioset it belongs to has already been destroyed due to improper ordering of operations involving atomic counters and wake-up calls. This leads to a NULL pointer dereference and kernel crash. The fix involved reordering calls to ensure bio_put is called before decrementing atomic counters to prevent freeing a bio into a destroyed bioset.
How can this vulnerability impact me? :
This vulnerability can cause the Linux kernel to crash due to a NULL pointer dereference, leading to system instability or denial of service. If exploited or triggered, it could cause unexpected system reboots or failures, impacting availability and reliability of systems running vulnerable kernel versions.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, update the Linux kernel to a version that includes the fix where bio_put is called before atomic_dec_and_test in the md subsystem. This prevents the crash in mempool_free. Avoid running the lvm test shell/lvchange-rebuild-raid.sh or similar operations that trigger this bug until the kernel is patched.