LiveActive security incident?Get immediate response
CVE Record

CVE-2024-40986: dmaengine: xilinx: xdma: Fix data synchronisation in xdma_channel_isr()

In the Linux kernel, the following vulnerability has been resolved: dmaengine: xilinx: xdma: Fix data synchronisation in xdma_channel_isr() Requests the vchan lock before using xdma->stop_request.

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

Security readout for executives and security teams

Plain-English summary

This CVE is a Linux kernel bug in the Xilinx XDMA DMA engine driver. The public record says an interrupt handler used a stop-request flag without first taking the virtual channel lock. The business risk is mainly for systems that run affected kernels and use Xilinx XDMA hardware or driver support.

Executive priority

Handle through normal kernel patch management, with higher attention for appliances, embedded systems, or servers using Xilinx XDMA. There is not enough public evidence to justify emergency action, but kernel synchronization bugs can affect system stability in specialized hardware environments.

Technical view

The fix changes xdma_channel_isr() to request the vchan lock before accessing xdma->stop_request, resolving a data synchronization issue in the Linux dmaengine Xilinx XDMA driver. The source bundle provides no CVSS score, CWE, crash impact, privilege boundary, or concrete exploit path.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions with the Xilinx XDMA dmaengine driver relevant to their hardware or build. Kernel branches around 6.9 are specifically indicated; source version data is incomplete and should be verified against vendor kernels.

Exploitation context

The bundle does not cite active exploitation, and KEV status is false. No public source in the bundle describes a proof of concept, attacker prerequisites, or weaponized exploitation. Treat this as a kernel reliability and safety issue until vendor guidance clarifies impact.

Researcher notes

The key issue is locking discipline around xdma->stop_request in xdma_channel_isr(). The public record is sparse: no CVSS, CWE, affected configuration details, or exploitability analysis are provided. Validation should focus on kernel commit lineage, downstream backports, and whether XDMA code is reachable on the target.

Mitigation direction

  • Update to a kernel or vendor build containing the referenced stable fixes.
  • Prioritize hosts using Xilinx XDMA hardware or loading the XDMA dmaengine driver.
  • For custom kernels, evaluate backporting the upstream locking fix.
  • Check Linux distribution and hardware vendor advisories for supported packages.
  • Test DMA workloads after patching to catch driver regressions.

Validation and detection

  • Inventory kernel versions across systems that may use Xilinx XDMA.
  • Confirm whether the XDMA dmaengine driver is built, loaded, or required.
  • Verify the referenced stable commit is present in the deployed kernel source.
  • Review vendor kernel changelogs for CVE-2024-40986 or the xdma_channel_isr fix.
  • Run normal regression tests for DMA-dependent applications after updating.
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-40986 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
2ADP 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

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux6a40fb8245965b481b4dcce011cd63f20bf91ee0, 6a40fb8245965b481b4dcce011cd63f20bf91ee0, 582ce5d734190d74e5ce9cd711cf6e964e1e7b29, 6.8.9unaffected
LinuxLinux6.9, 0, 6.9.7, 6.10affected
Weakness

CWE details

No CWE listed

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