https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 06:55:21 +0000 https://vulnerability.circl.lu/vuln/cve-2024-26899 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>block: fix deadlock between bd_link_disk_holder and partition scan</p> <p>&#39;open_mutex&#39; 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.</p> <p>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 &#39;open_mutex&#39;, such as scanning partitions, can cause deadlocks. For example, in raid:</p> <p>T1 T2 bdev_open_by_dev lock open_mutex [1] ... efi_partition ... md_submit_bio md_ioctl mddev_syspend -&gt; suspend all io md_add_new_disk bind_rdev_to_array bd_link_disk_holder try lock open_mutex [2] md_handle_request -&gt; wait mddev_resume</p> <p>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.</p> <p>Fix it by introducing a local mutex &#39;blk_holder_mutex&#39; to replace &#39;open_mutex&#39;.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>block: fix deadlock between bd_link_disk_holder and partition scan</p> <p>&#39;open_mutex&#39; 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.</p> <p>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 &#39;open_mutex&#39;, such as scanning partitions, can cause deadlocks. For example, in raid:</p> <p>T1 T2 bdev_open_by_dev lock open_mutex [1] ... efi_partition ... md_submit_bio md_ioctl mddev_syspend -&gt; suspend all io md_add_new_disk bind_rdev_to_array bd_link_disk_holder try lock open_mutex [2] md_handle_request -&gt; wait mddev_resume</p> <p>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.</p> <p>Fix it by introducing a local mutex &#39;blk_holder_mutex&#39; to replace &#39;open_mutex&#39;.</p> https://vulnerability.circl.lu/vuln/cve-2024-26899