CVE-2024-26790: dmaengine: fsl-qdma: fix SoC may hang on 16 byte unaligned read
In the Linux kernel, the following vulnerability has been resolved:
dmaengine: fsl-qdma: fix SoC may hang on 16 byte unaligned read
There is chip (ls1028a) errata:
The SoC may hang on 16 byte unaligned read transactions by QDMA.
Unaligned read transactions initiated by QDMA may stall in the NOC
(Network On-Chip), causing a deadlock condition. Stalled transactions will
trigger completion timeouts in PCIe controller.
Workaround:
Enable prefetch by setting the source descriptor prefetchable bit
( SD[PF] = 1 ).
Implement this workaround.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel availability issue tied to specific SoC DMA hardware. On affected systems, certain unaligned QDMA reads can hang the SoC by deadlocking transactions inside the chip fabric, disrupting PCIe-related operation. Exposure appears hardware-specific, not broad across all Linux deployments.
Executive priority
Treat as a targeted availability risk for specialized Linux-based hardware, not a broad enterprise emergency. Patch during the next maintenance cycle for affected appliances, network equipment, embedded systems, or edge devices where unexpected hangs create operational impact.
Technical view
CVE-2024-26790 fixes the fsl-qdma driver for an LS1028A erratum: 16-byte unaligned QDMA read transactions may stall in the Network-On-Chip and cause deadlock, with PCIe completion timeouts. The kernel fix implements the documented workaround by setting the source descriptor prefetchable bit, SD[PF].
Likely exposure
Likely limited to Linux systems using the Freescale/NXP fsl-qdma driver on affected LS1028A-class SoCs or vendor kernels carrying the vulnerable code. General Linux servers without this QDMA hardware are unlikely to be exposed based on the supplied sources.
Exploitation context
The provided sources do not report active exploitation, KEV listing, public exploit code, or remote attack details. The issue is described as a hardware erratum reachable through QDMA unaligned read behavior, so practical risk depends on whether local workloads or devices can trigger those transactions.
Researcher notes
The public record lacks CVSS, CWE, exploitability analysis, and detailed affected-version ranges beyond Linux kernel references. Research should focus on hardware presence, fsl-qdma code lineage, stable backport status, and whether local DMA-capable paths can reliably trigger unaligned read transactions.
Mitigation direction
Apply Linux kernel updates containing the referenced stable fixes.
Review Debian LTS or vendor advisories for matching kernel package updates.
Prioritize affected embedded, edge, and appliance systems using LS1028A hardware.
If patching is delayed, check vendor guidance for operational workarounds.
Validation and detection
Inventory systems for LS1028A-class SoCs and fsl-qdma driver usage.
Map running kernel versions to fixed stable commits or distro package advisories.
Check logs for PCIe completion timeouts or DMA-related hangs on exposed hardware.
Confirm updated kernels include the SD[PF] prefetch workaround.
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-26790 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.