https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 01 Oct 2026 22:12:58 +0000 https://vulnerability.circl.lu/vuln/cve-2024-35808 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>md/dm-raid: don&#39;t call md_reap_sync_thread() directly</p> <p>Currently md_reap_sync_thread() is called from raid_message() directly without holding &#39;reconfig_mutex&#39;, this is definitely unsafe because md_reap_sync_thread() can change many fields that is protected by &#39;reconfig_mutex&#39;.</p> <p>However, hold &#39;reconfig_mutex&#39; here is still problematic because this will cause deadlock, for example, commit 130443d60b1b (&#34;md: refactor idle/frozen_sync_thread() to fix deadlock&#34;).</p> <p>Fix this problem by using stop_sync_thread() to unregister sync_thread, like md/raid did.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>md/dm-raid: don&#39;t call md_reap_sync_thread() directly</p> <p>Currently md_reap_sync_thread() is called from raid_message() directly without holding &#39;reconfig_mutex&#39;, this is definitely unsafe because md_reap_sync_thread() can change many fields that is protected by &#39;reconfig_mutex&#39;.</p> <p>However, hold &#39;reconfig_mutex&#39; here is still problematic because this will cause deadlock, for example, commit 130443d60b1b (&#34;md: refactor idle/frozen_sync_thread() to fix deadlock&#34;).</p> <p>Fix this problem by using stop_sync_thread() to unregister sync_thread, like md/raid did.</p> https://vulnerability.circl.lu/vuln/cve-2024-35808