CVE-2024-35808: md/dm-raid: don't call md_reap_sync_thread() directly

Severity: medium (CVSS 5.5 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.2% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2024-05-17 · updated 2026-08-04
Weakness: CWE-667

Description

In the Linux kernel, the following vulnerability has been resolved: md/dm-raid: don't call md_reap_sync_thread() directly Currently md_reap_sync_thread() is called from raid_message() directly without holding 'reconfig_mutex', this is definitely unsafe because md_reap_sync_thread() can change many fields that is protected by 'reconfig_mutex'. However, hold 'reconfig_mutex' here is still problematic because this will cause deadlock, for example, commit 130443d60b1b ("md: refactor idle/frozen_sync_thread() to fix deadlock"). Fix this problem by using stop_sync_thread() to unregister sync_thread, like md/raid did.

Affected products

Linux kernel: from 3.10 before 6.7.12; from 6.8 before 6.8.3 — fixed in 6.7.12, 6.8.3

How to fix

Upgrade to a fixed version: Linux kernel 6.7.12, 6.8.3. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2024-35808 or the next vulnerability affects your stack