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.
Security readout for executives and security teams
Plain-English summary
A flaw in Linux’s device-mapper RAID handling can unsafely change protected RAID synchronization state. A user who already has low-privileged local access could potentially compromise confidentiality, integrity, or availability. It is not described as remotely exploitable.
Executive priority
Treat this as high priority on systems combining affected kernels, dm-raid usage, and access by untrusted local users. Schedule an accelerated kernel update for those hosts. Systems without dm-raid or without plausible local access are lower urgency, but should still follow supported vendor patch guidance.
Technical view
raid_message() called md_reap_sync_thread() without holding reconfig_mutex, allowing unsafe changes to protected fields. Acquiring that mutex directly could instead deadlock. The upstream correction uses stop_sync_thread() to unregister the synchronization thread consistently with md/raid behavior.
Likely exposure
Exposure is most relevant to systems running an affected Linux kernel and using md/dm-raid functionality. The bundle identifies releases including 3.10, 6.7.12, 6.8.3, and 6.9, but does not clearly define complete version boundaries or distribution backports.
Exploitation context
The CVSS vector indicates a local, low-complexity attack requiring low privileges and no user interaction. The bundle marks this CVE as absent from KEV and provides no evidence of active exploitation or a public exploit. Internet exposure alone does not provide the required local access.
Researcher notes
The source describes unsafe synchronization-state handling but does not specify a CWE, concrete corruption primitive, or demonstrated exploitation outcome. Do not infer memory corruption or privilege escalation solely from the 7.8 CVSS score. Exact affected and fixed package versions require distribution-specific confirmation.
Mitigation direction
Install a vendor-supported kernel update incorporating the referenced upstream stable fix.
Confirm the distribution’s package advisory because vendors may backport fixes without changing major kernel versions.
Restrict unnecessary local accounts and shell access until affected systems are updated.
Prioritize shared, multi-user, and other hosts where untrusted users can obtain local access.
Validation and detection
Inventory running kernel versions and identify hosts configured with md or device-mapper RAID.
Map each vendor kernel package to its advisory or included backported commits.
After updating and rebooting, confirm the fixed kernel is actually running.
Review RAID-related logs, recognizing that the supplied sources provide no vulnerability-specific detection indicator.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-35808 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.