Answer in brief
CVE-2024-35808 records a Unknown severity vulnerability in md/dm-raid: don't call md_reap_sync_thread() directly. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=be83651f0050ca8621d58d35dad558e9c45cb18f <347dcdc15a1706f61aa545ae498ededdf31aeebc || >=be83651f0050ca8621d58d35dad558e9c45cb18f <9e59b8d76ff511505eb0dd1478329f09e0f04669 || >=be83651f0050ca8621d58d35dad558e9c45cb18f <cd32b27a66db8776d8b8e82ec7d7dde97a8693b0 | 347dcdc15a1706f61aa545ae498ededdf31aeebc, 9e59b8d76ff511505eb0dd1478329f09e0f04669, cd32b27a66db8776d8b8e82ec7d7dde97a8693b0 |
| Linux/Linuxgeneric | 3.10 | Not reported |
Published upstream
May 17, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-35808 records a Unknown severity vulnerability in md/dm-raid: don't call md_reap_sync_thread() directly. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=be83651f0050ca8621d58d35dad558e9c45cb18f <347dcdc15a1706f61aa545ae498ededdf31aeebc || >=be83651f0050ca8621d58d35dad558e9c45cb18f <9e59b8d76ff511505eb0dd1478329f09e0f04669 || >=be83651f0050ca8621d58d35dad558e9c45cb18f <cd32b27a66db8776d8b8e82ec7d7dde97a8693b0 | 347dcdc15a1706f61aa545ae498ededdf31aeebc, 9e59b8d76ff511505eb0dd1478329f09e0f04669, cd32b27a66db8776d8b8e82ec7d7dde97a8693b0 |
| Linux/Linuxgeneric | 3.10 | Not reported |
Published upstream
May 17, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.