CVE-2024-26899block: fix deadlock between bd_link_disk_holder and partition scan
- 5.5MediumCVSS base score
- 0.21%Exploitation in 30 daysEPSS · top 89% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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'.
Timeline
ID reserved
By Linux
- 58 days later
· 58 days later
Published
- 2 years later
· 2 years later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Modified | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.21% · top 89% of all CVEs (16 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected 1b0a2d950ee2a54aa04fb31ead32144be0bbf690 – < 1e5c5b0abaee7b62a10b9707a62083b71ad21f62
- affected 1b0a2d950ee2a54aa04fb31ead32144be0bbf690 – < 5a87c1f7993bc8ac358a3766bac5dc7126e01e98
- affected 1b0a2d950ee2a54aa04fb31ead32144be0bbf690 – < 03f12122b20b6e6028e9ed69030a49f9cffcbb75
- affected 6.7
- unaffected < 6.7
- unaffected 6.7.11 – ≤ 6.7.*
- unaffected 6.8.2 – ≤ 6.8.*
- unaffected 6.9 – ≤ *
References
References3
- https://git.kernel.org/stable/c/1e5c5b0abaee7b62a10b9707a62083b71ad21f62 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/5a87c1f7993bc8ac358a3766bac5dc7126e01e98 (opens in a new tab)x_transferred
- https://git.kernel.org/stable/c/03f12122b20b6e6028e9ed69030a49f9cffcbb75 (opens in a new tab)x_transferred
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2024-24161 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2024-26899)Record last updated .