CVE-2024-26899 Details
Description
In the Linux kernel, the following vulnerability has been resolved: block: fix deadlock between bd_link_disk_holder and partition scan 'open_mutex' of gendisk is used to protect open/close block devices. But in bd_link_disk_holder(), it is used to protect the creation of symlink between holding disk and slave bdev, which introduces some issues. When bd_link_disk_holder() is called, the driver is usually in the process of initialization/modification and may suspend submitting io. At this time, any io hold 'open_mutex', such as scanning partitions, can cause deadlocks. For example, in raid: T1 T2 bdev_open_by_dev lock open_mutex [1] ... efi_partition ... md_submit_bio md_ioctl mddev_syspend -> suspend all io md_add_new_disk bind_rdev_to_array bd_link_disk_holder try lock open_mutex [2] md_handle_request -> wait mddev_resume T1 scan partition, T2 add a new device to raid. T1 waits for T2 to resume mddev, but T2 waits for open_mutex held by T1. Deadlock occurs. Fix it by introducing a local mutex 'blk_holder_mutex' to replace 'open_mutex'.
A deadlock vulnerability has been identified in the Linux kernel's block device management, specifically within the 'bd_link_disk_holder' function of the block holder subsystem. This issue arises because 'open_mutex' is used to manage the open and close operations of block devices. However, during the linking of disk holders, 'open_mutex' inadvertently protects the creation of symbolic links between the master disk and its slave block devices. This can lead to deadlocks, particularly when partition scanning holds 'open_mutex' while another thread attempts to link a disk holder, creating a circular wait condition. The vulnerability affects the Linux kernel stable tree.
The vulnerability has been addressed by introducing a new local mutex, 'blk_holder_mutex', to replace the original 'open_mutex' in the 'bd_link_disk_holder' function. This change prevents the deadlock by allowing partition scans and disk linking operations to proceed without interfering with each other.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Jun 12, 2024References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-667 | Improper Locking | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 6.7, < 6.7.11 >= 6.8, < 6.8.2 |
CPE
Remediation
| |
Change History
7 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Nov 21, 2024 | CVE Modified | CVE |
| May 29, 2024 | CVE Modified | kernel.org |
| May 14, 2024 | CVE Modified | kernel.org |
| Apr 29, 2024 | Initial Analysis | [email protected] |
| Apr 17, 2024 | New CVE Received | kernel.org |