LiveActive security incident?Get immediate response
CVE Record

CVE-2024-43820: dm-raid: Fix WARN_ON_ONCE check for sync_thread in raid_resume

In the Linux kernel, the following vulnerability has been resolved: dm-raid: Fix WARN_ON_ONCE check for sync_thread in raid_resume rm-raid devices will occasionally trigger the following warning when being resumed after a table load because DM_RECOVERY_RUNNING is set: WARNING: CPU: 7 PID: 5660 at drivers/md/dm-raid.c:4105 raid_resume+0xee/0x100 [dm_raid] The failing check is: WARN_ON_ONCE(test_bit(MD_RECOVERY_RUNNING, &mddev->recovery)); This check is designed to make sure that the sync thread isn't registered, but md_check_recovery can set MD_RECOVERY_RUNNING without the sync_thread ever getting registered. Instead of checking if MD_RECOVERY_RUNNING is set, check if sync_thread is non-NULL.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue affects dm-raid resume handling. In some resume-after-table-load cases, the kernel can trigger a warning because it checks a recovery flag rather than whether a sync thread actually exists. The public record does not describe data loss, privilege escalation, or remote exploitation.

Executive priority

Treat as a targeted Linux storage-stack maintenance issue unless vendor guidance adds higher impact. Prioritize affected dm-raid systems during normal kernel patch cycles, especially where storage reliability and alert noise matter.

Technical view

The dm-raid raid_resume path used WARN_ON_ONCE on MD_RECOVERY_RUNNING. The source says md_check_recovery can set that bit even when sync_thread was never registered. The fix changes the condition to check whether sync_thread is non-NULL instead of relying on the recovery flag.

Likely exposure

Exposure appears limited to Linux systems using dm-raid/device-mapper RAID on affected kernel versions or commits. The bundle names Linux kernel 6.9 through 6.11-era entries and fixed stable commits, but the provided version data is incomplete.

Exploitation context

No active exploitation is cited, and KEV is false. The provided sources describe an occasional kernel warning during dm-raid resume after table load, not a known public exploit path or attacker-controlled workflow.

Researcher notes

Evidence supports a logic correction in dm-raid warning validation, not a demonstrated exploit. The key uncertainty is impact: the public description does not state confidentiality, integrity, availability consequences, CVSS, CWE, or exploitability details.

Mitigation direction

  • Check the Linux vendor or distribution advisory for fixed kernel packages.
  • Prioritize updates on systems using dm-raid or device-mapper RAID.
  • Apply kernels containing the referenced stable fixes when available.
  • Monitor kernel logs for repeated dm_raid raid_resume warnings.

Validation and detection

  • Inventory Linux kernel versions and dm-raid usage across storage hosts.
  • Compare running kernels against vendor advisories and the referenced stable commits.
  • Review logs for dm_raid raid_resume WARN_ON_ONCE messages.
  • Confirm updated systems no longer emit the warning during dm-raid resume operations.
Prepared
Confidence
medium
Sources
4

Public sources used

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-43820 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

0CVSS vectors
3Timeline events
1ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux16c4770c75b1223998adbeb7286f9a15c65fba73, 16c4770c75b1223998adbeb7286f9a15c65fba73, af916cb66a80597f3523bc85812e790bcdcfd62b, eaa8fc9b092837cf2c754bde1a15d784ce9a85ab, 6.7.12, 6.8.3unaffected
LinuxLinux6.9, 0, 6.10.3, 6.11affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.