CVE-2022-50752
Double Free Vulnerability in Linux Kernel md/raid5 Component
Publication date: 2025-12-24
Last updated on: 2025-12-24
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a double free bug in the Linux kernel's md/raid5 subsystem. It occurs because of an unnecessary bio_put() call in the raid5_read_one_chunk() function when handling chunk-sized reads on disks with bad blocks. The error path was changed so that the bio_put() call became redundant, leading to the same bio object being freed twice. This can cause kernel memory corruption or crashes.
How can this vulnerability impact me? :
The double free vulnerability can lead to kernel memory corruption, which may cause system instability, crashes, or potential denial of service. In some cases, it could be exploited to execute arbitrary code with kernel privileges, compromising system security.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by observing kernel logs for duplicate bio free/put errors, specifically messages like 'BUG bio-200 (Not tainted): Object already free' related to raid5_read_one_chunk operations. Monitoring dmesg or kernel logs for such error traces can help identify the issue. For example, you can use the command 'dmesg | grep -i "bio_put"' or 'journalctl -k | grep -i "bio_put"' to look for relevant error messages.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves updating the Linux kernel to a version where the unnecessary bio_put() call in raid5_read_one_chunk() has been removed, as this fixes the double free issue. Until the patch is applied, avoid running chunk-sized reads on disks with bad blocks in RAID5 configurations to reduce the chance of triggering the bug.