LiveActive security incident?Get immediate response
CVE Record

CVE-2024-27409: dmaengine: dw-edma: HDMA: Add sync read before starting the DMA transfer in remote setup

In the Linux kernel, the following vulnerability has been resolved: dmaengine: dw-edma: HDMA: Add sync read before starting the DMA transfer in remote setup The Linked list element and pointer are not stored in the same memory as the HDMA controller register. If the doorbell register is toggled before the full write of the linked list a race condition error will occur. In remote setup we can only use a readl to the memory to assure the full write has occurred.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A timing flaw in a Linux DMA driver can start a transfer before its linked-list data is fully written. On systems using the affected DesignWare eDMA HDMA remote setup, this race could corrupt DMA operations and may compromise confidentiality, integrity, or availability. Exploitation requires local access with some privileges; ordinary Linux systems may not use the affected hardware path.

Executive priority

Treat this as a prompt, targeted remediation rather than an internet-wide emergency. First identify systems using the affected DMA path, especially shared or locally accessible infrastructure, then apply supported kernel updates. Potential impact is high, but local access and hardware-path prerequisites reduce broad exposure, and the supplied evidence does not show active exploitation.

Technical view

The dw-edma HDMA remote path can toggle the doorbell before linked-list elements and pointers become fully visible to the controller. The upstream resolution adds a synchronizing memory read before transfer initiation. The supplied CVSS 3.1 score is 7.8, with local, low-complexity, low-privilege exploitation and potentially high impact across confidentiality, integrity, and availability.

Likely exposure

Exposure is limited to Linux systems running an affected kernel and exercising the dw-edma HDMA remote-setup path. The bundle identifies affected releases including 6.5, 6.6.21, 6.7.9, and 6.8, but its version formatting does not establish reliable ranges. Confirm hardware, driver usage, and backported patch status with the distribution or appliance vendor.

Exploitation context

The supplied vector requires local access and low privileges, without user interaction. The bundle marks KEV false and provides no evidence of active exploitation or a public exploit. Practical reachability likely depends on the affected DMA hardware and remote-setup path being present and usable; the sources do not establish how commonly that condition occurs.

Researcher notes

No CWE is assigned in the bundle. The defect is a write-ordering race between linked-list memory and the HDMA doorbell operation; the fix introduces a synchronizing read. Exact vulnerable and fixed version boundaries are unclear from the supplied version data, so commit-level comparison and vendor backport confirmation are more reliable than version-string matching alone.

Mitigation direction

  • Apply a vendor-supported kernel containing the applicable upstream stable fix.
  • Check distribution or appliance advisories for backported patch status.
  • Prioritize systems using dw-edma HDMA remote setup.
  • Restrict unnecessary local account access while remediation is pending.
  • If patch status remains unclear, obtain explicit guidance from the system vendor.

Validation and detection

  • Inventory kernel versions on systems with relevant DMA hardware.
  • Determine whether the dw-edma HDMA driver and remote setup are used.
  • Compare vendor kernel patches against the three referenced stable commits.
  • Confirm the updated kernel is active after maintenance.
  • Run representative DMA workloads and standard regression tests after updating.
Prepared
Confidence
medium
Sources
5

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-27409 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
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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.

1CVSS vectors
3Timeline events
2ADP providers
4Source links

SSVC decision data

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

CVSS vector scores

1 official score

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.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2024-27409Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxe74c39573d35e9ac441090ff8183aa3dc2540649, e74c39573d35e9ac441090ff8183aa3dc2540649, e74c39573d35e9ac441090ff8183aa3dc2540649unaffected
LinuxLinux6.5, 0, 6.6.21, 6.7.9, 6.8affected
Weakness

CWE details

No CWE listed

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