LiveActive security incident?Get immediate response
CVE Record

CVE-2024-43856: dma: fix call order in dmam_free_coherent

In the Linux kernel, the following vulnerability has been resolved: dma: fix call order in dmam_free_coherent dmam_free_coherent() frees a DMA allocation, which makes the freed vaddr available for reuse, then calls devres_destroy() to remove and free the data structure used to track the DMA allocation. Between the two calls, it is possible for a concurrent task to make an allocation with the same vaddr and add it to the devres list. If this happens, there will be two entries in the devres list with the same vaddr and devres_destroy() can free the wrong entry, triggering the WARN_ON() in dmam_match. Fix by destroying the devres entry before freeing the DMA allocation. kokonut //net/encryption http://sponge2/b9145fe6-0f72-4325-ac2f-a84d81075b03

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue is a race in DMA memory cleanup. Under concurrent activity, the kernel can free or remove the wrong internal tracking record for a DMA allocation, leading to a kernel warning and possible driver or system instability. Public sources do not provide a CVSS score or confirmed exploitation.

Executive priority

Treat this as a kernel maintenance and vendor-tracking item unless your environment depends heavily on custom drivers or embedded Linux devices. The public record lacks exploitation evidence and severity scoring, but kernel defects can be operationally disruptive when left unpatched.

Technical view

dmam_free_coherent() freed the DMA allocation before removing its devres tracking entry. A concurrent allocation could reuse the same virtual address and create duplicate devres entries, so devres_destroy() could match and free the wrong entry, triggering WARN_ON() in dmam_match. The fix changes the call order.

Likely exposure

Exposure is limited to Linux systems running affected kernel versions or vendor products that embed those kernels. Internet reachability is not indicated by the sources; this appears tied to local kernel, driver, and device DMA behavior.

Exploitation context

The CVE source says KEV is false and provides no evidence of active exploitation. The public description identifies a concurrency flaw but does not describe an exploit path, attacker prerequisites, or practical impact beyond incorrect devres cleanup and WARN_ON().

Researcher notes

The core condition is a race between freeing DMA memory and destroying the devres tracking entry. Analysis should focus on affected kernel branches, downstream backports, and drivers using dmam_free_coherent(). Public evidence is insufficient to claim remote exploitability or broad privilege-escalation impact.

Mitigation direction

  • Apply the relevant Linux stable kernel fix or vendor kernel update.
  • Check Debian LTS and device vendor advisories for packaged fixes.
  • Prioritize embedded, industrial, and appliance kernels that lag upstream stable releases.
  • Avoid direct wrangler-style assumptions; follow vendor-specific kernel update guidance.

Validation and detection

  • Inventory Linux kernel versions across servers, appliances, and embedded systems.
  • Compare deployed kernels against vendor advisories and listed stable commits.
  • Confirm whether downstream distributions backported the dmam_free_coherent() fix.
  • Review kernel logs for related DMA/devres WARN_ON() events.
Prepared
Confidence
medium
Sources
12

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-43856 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
3ADP providers
12Source 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
CVECVE Program Container
siemens-SADPADP container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux9ac7849e35f705830f7b016ff272b0ff1f7ff759, 9ac7849e35f705830f7b016ff272b0ff1f7ff759, 9ac7849e35f705830f7b016ff272b0ff1f7ff759, 9ac7849e35f705830f7b016ff272b0ff1f7ff759, 9ac7849e35f705830f7b016ff272b0ff1f7ff759, 9ac7849e35f705830f7b016ff272b0ff1f7ff759, 9ac7849e35f705830f7b016ff272b0ff1f7ff759, 9ac7849e35f705830f7b016ff272b0ff1f7ff759unaffected
LinuxLinux2.6.21, 0, 4.19.320, 5.4.282, 5.10.224, 5.15.165, 6.1.103, 6.6.44, 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.