LiveActive security incident?Get immediate response
CVE Record

CVE-2026-43064: dmaengine: idxd: Fix not releasing workqueue on .release()

In the Linux kernel, the following vulnerability has been resolved: dmaengine: idxd: Fix not releasing workqueue on .release() The workqueue associated with an DSA/IAA device is not released when the object is freed.

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 is a cleanup bug: a DSA/IAA device workqueue may not be released when its object is freed. The public record does not state a severity, CVSS score, direct business impact, or active exploitation. Treat it as a kernel maintenance risk until your Linux vendor maps it to shipped packages.

Executive priority

Handle through normal kernel patch governance unless vendor guidance raises severity. Prioritize accelerator-enabled servers and platforms with strict uptime planning, because kernel updates often require reboot coordination.

Technical view

CVE-2026-43064 affects the Linux kernel dmaengine idxd code. The release path did not release the workqueue associated with a DSA/IAA device when the object was freed. Upstream stable commits are referenced as fixes, but the source bundle does not provide exploitability analysis, CVSS, CWE, or distro package status.

Likely exposure

Exposure is most likely on Linux systems running affected kernel builds with DSA/IAA device support. Systems without the relevant kernel code path or hardware use may have lower practical exposure, but the provided sources do not prove that absence removes risk.

Exploitation context

The bundle says KEV is false and provides no cited evidence of exploitation. It also does not describe attacker prerequisites, impact class, or exploitation method. Do not assume active exploitation or remote exploitability from the available evidence.

Researcher notes

The record is sparse: no CVSS, CWE, exploit status, or detailed impact is provided. Analysis should focus on source review of the referenced stable commits, kernel version mapping, and vendor backport confirmation rather than assumptions about exploitability.

Mitigation direction

  • Check Linux vendor advisories for package-specific fixed versions.
  • Upgrade kernels to builds containing the referenced upstream stable fixes.
  • Prioritize systems using DSA/IAA devices or the idxd driver.
  • Track distro backports because fixed package versions may differ from upstream versions.

Validation and detection

  • Inventory running kernel versions across Linux assets.
  • Identify hosts with DSA/IAA hardware or idxd driver usage.
  • Compare installed kernels against vendor-fixed package advisories.
  • Confirm patched systems rebooted into the fixed kernel.
Prepared
Confidence
medium
Sources
7

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-2026-43064 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
0ADP providers
6Source links

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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux47c16ac27d4cb664cee53ee0b9b7e2f907923fb3, 47c16ac27d4cb664cee53ee0b9b7e2f907923fb3, 47c16ac27d4cb664cee53ee0b9b7e2f907923fb3, 47c16ac27d4cb664cee53ee0b9b7e2f907923fb3, 47c16ac27d4cb664cee53ee0b9b7e2f907923fb3, 3f0e87eb9680975184e98aed0e8866b4442a31f6, a13e4cf29da68630a116c1309072a265ade9566d, 5.11.22, 5.12.5unaffected
LinuxLinux5.13, 0, 6.6.131, 6.12.80, 6.18.21, 6.19.11, 7.0affected
Weakness

CWE details

No CWE listed

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