LiveActive security incident?Get immediate response
CVE Record

CVE-2024-38629: dmaengine: idxd: Avoid unnecessary destruction of file_ida

In the Linux kernel, the following vulnerability has been resolved: dmaengine: idxd: Avoid unnecessary destruction of file_ida file_ida is allocated during cdev open and is freed accordingly during cdev release. This sequence is guaranteed by driver file operations. Therefore, there is no need to destroy an already empty file_ida when the WQ cdev is removed. Worse, ida_free() in cdev release may happen after destruction of file_ida per WQ cdev. This can lead to accessing an id in file_ida after it has been destroyed, resulting in a kernel panic. Remove ida_destroy(&file_ida) to address these issues.

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

Security readout for executives and security teams

Plain-English summary

CVE-2024-38629 is a Linux kernel bug in the idxd DMA engine driver that can trigger a kernel panic. In business terms, affected systems could crash if this driver path is exercised, causing availability impact rather than confirmed data theft or remote takeover.

Executive priority

Treat as an availability risk for affected Linux infrastructure, especially systems using idxd. Patch through normal kernel maintenance with higher priority where unexpected crashes would disrupt production services.

Technical view

The idxd driver destroys file_ida when a workqueue character device is removed, although file_ida is allocated on cdev open and freed on cdev release. If ida_free() runs after ida_destroy(), the kernel may access a destroyed ID allocator and panic. The fix removes ida_destroy(&file_ida).

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions with the dmaengine idxd driver path in use. The bundle lists Linux kernel versions including 6.4, 6.6.33, 6.9.4, and 6.10 as affected, but downstream distribution status must be confirmed separately.

Exploitation context

The source bundle does not cite active exploitation, public exploit code, or KEV listing. The described impact is a kernel panic caused by driver lifecycle ordering. Evidence is insufficient to claim remote exploitability or privilege escalation.

Researcher notes

The root cause is object lifecycle mismatch in idxd WQ cdev teardown. The CVE record provides upstream stable commit references but no CVSS, CWE, exploit evidence, or downstream distribution matrix. Validation should focus on kernel version, driver usage, and patch backport evidence.

Mitigation direction

  • Check Linux vendor advisories for CVE-2024-38629 and affected downstream kernels.
  • Update to a vendor-supported kernel containing the referenced stable fix.
  • Prioritize systems using Intel idxd or related DMA engine functionality.
  • Avoid direct wrangler or deployment shortcuts; follow normal tested patch rollout procedures.
  • Monitor for kernel panic reports on systems using affected kernels.

Validation and detection

  • Inventory kernel versions across Linux hosts and compare with vendor CVE status.
  • Confirm whether the idxd driver is present or used on prioritized systems.
  • Verify patched kernels include the file_ida ida_destroy removal fix.
  • Review system logs for recent kernel panics involving idxd or dmaengine.
  • Track vendor backport status rather than relying only on upstream version numbers.
Prepared
Confidence
medium
Sources
5

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-38629 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
4Source 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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxe6fd6d7e5f0fe4a17a08e892afb5db800e7794ec, e6fd6d7e5f0fe4a17a08e892afb5db800e7794ec, e6fd6d7e5f0fe4a17a08e892afb5db800e7794ecunaffected
LinuxLinux6.4, 0, 6.6.33, 6.9.4, 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.