In the Linux kernel, the following vulnerability has been resolved:
dmaengine: ti: k3-udma-glue: Fix of_k3_udma_glue_parse_chn_by_id()
The of_k3_udma_glue_parse_chn_by_id() helper function erroneously
invokes "of_node_put()" on the "udmax_np" device-node passed to it,
without having incremented its reference count at any point. Fix it.
Security readout for executives and security teams
Plain-English summary
A Linux kernel driver helper mishandles a device-tree reference, potentially releasing it prematurely. A local, low-privileged user may be able to trigger serious confidentiality, integrity, or availability consequences on affected systems. Exposure depends on the affected TI K3 UDMA glue code being present and reachable.
Executive priority
Treat as a high-priority kernel maintenance issue on exposed TI K3-based systems. Accelerate patching where untrusted users or workloads can execute locally; otherwise address through the normal urgent patch cycle after confirming driver and version exposure.
Technical view
The function of_k3_udma_glue_parse_chn_by_id() calls of_node_put() on the supplied udmax_np device node without first acquiring a corresponding reference. The kernel fix removes this incorrect reference release. The supplied CVSS 3.1 score is 7.8, with local access and low privileges required.
Likely exposure
Prioritize Linux systems matching the affected version or commit ranges in the CVE record, particularly systems using the TI K3 UDMA glue driver. The bundled version representation is ambiguous, so determine exposure using vendor advisories and fix-commit ancestry rather than version strings alone.
Exploitation context
The CVSS vector describes a local, low-complexity, low-privilege attack requiring no user interaction. The source bundle provides no evidence of public exploitation or exploit availability, and the CVE is not listed as KEV.
Researcher notes
The defect is an unbalanced device-node reference release in a TI DMA-engine helper. The sources establish the coding error and corrective commits but do not document a demonstrated exploitation chain, affected runtime configurations, or observed attacks. Branch-specific reachability and backport status require local verification.
Mitigation direction
Install a vendor-supported kernel update containing the applicable stable fix.
Verify whether either referenced fix commit, or its vendor backport, is present.
Restrict unnecessary local account and code-execution access until affected systems are updated.
Consult the distribution or device vendor for branch-specific remediation guidance.
Validation and detection
Inventory kernel versions and vendor build identifiers across Linux systems.
Check kernel source or package metadata for the applicable fix or backport.
Determine whether the TI K3 UDMA glue driver is built and used.
After updating, confirm the corrected kernel boots and affected hardware functions normally.
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-40991 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
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.