Look up another CVE · open CVE-2026-72148 in the interactive tracker
CVE-2026-72148
dmaengine: dw-edma: Add spinlock to protect DONE_INT_MASK and ABORT_INT_MASK
Published 2026-08-15 (2 months ago) by the Linux kernel CNA. Subsystem drivers/dma. Debian urgency: not yet assigned.
Debian does not build this code. The per-release build detail is under "Where it lives" below.
What to do, per Debian release
Debian's own status for CVE-2026-72148 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | fixed | 6.1.180-1 | Update the kernel and reboot. Fixed in 6.1.180-1. A running kernel keeps the old code until the machine restarts. |
| Debian 13trixie | fixed | 6.12.100-1 | Update the kernel and reboot. Fixed in 6.12.100-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 7.1.5-1 | Update the kernel and reboot. Fixed in 7.1.5-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.1.5-1 | Update the kernel and reboot. Fixed in 7.1.5-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
The DONE_INT_MASK and ABORT_INT_MASK registers are shared by all DMA channels, and modifying them requires a read-modify-write sequence. Because this operation is not atomic, concurrent calls to dw_edma_v0_core_start() can introduce race conditions if two channels update these registers simultaneously. Add a spinlock to serialize access to these registers and prevent race conditions. [den: update dw_edma.lock comment]
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
drivers/dma/dw-edma/dw-edma-core.h
drivers/dma/dw-edma/dw-edma-v0-core.c
- What this is
- DESIGNWARE EDMA CORE IP DRIVERMAINTAINERS section matched on drivers/dma/dw-edma/ · dmaengine@vger.kernel.org · Maintained
- Kernel module
- none to look for. The file would have gone into dw_edma, and Debian does not compile it into that module, so finding dw_edma in lsmod would say nothing about this CVE.
Check it on the machine
grep -wE 'CONFIG_DMADEVICES|CONFIG_DW_EDMA' /boot/config-$(uname -r)Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.
Show whether Debian builds this, per release
Debian does not build this code. In 4 releases below, every kernel flavour Debian publishes has the switch off, so the vulnerable file is compiled into no kernel binary Debian ships.
- bookworm, trixie, forky, sidn
- n
- not enabled on any flavour - this release does not build the code
- Build switches
- CONFIG_DMADEVICES, CONFIG_DW_EDMA
- Reads as
- all on means the file is compiled; any one off means it is not.
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages
Signals
- Published
- 2026-08-15 (2 months ago)source
- CVSS
- 8.8 high
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:Hsource recompute it - Attack vector
- adjacent network (AV:A)source
- EPSS
- 0.33%, higher than 24.5% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- Subsystem
- drivers/dma
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 5.3 | 5.10.266 | 3989b4775bc2 |
| 5.3 | 5.15.217 | f60c7463d44f |
| 5.3 | 6.1.178 | 2247cc25a91f |
| 5.3 | 6.6.145 | 3ee0f478bb29 |
| 5.3 | 6.12.97 | 21a9834f56d6 |
| 5.3 | 6.18.40 | ddbc4a8a4fe2 |
| 5.3 | 7.1.5 | 1553ca96e9df |
| 5.3 | 7.2 | 8ffba0171c6b |
Why the CNA scored it this way
Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source
- AV:AAttack vector, adjacent network
- On PCIe endpoint SoCs (R-Car Gen4, DWC EP) the dw-edma v0 engine is driven when a physically connected PCIe root host initiates endpoint DMA (e.g. pci-epf-mhi); that host peer needs no network path to the victim, fitting Adjacent attack vector.
- AC:LAttack complexity, low
- The race needs only two eDMA channels starting their first chunk concurrently; an attacker controls both sides by issuing parallel DMA requests or timing concurrent completions, with no luck-dependent layout or rare config.
- PR:NPrivileges required, none
- In the highest-impact PCIe EP deployment a malicious or compromised upstream host triggers concurrent endpoint DMA through BAR/MHI traffic without any local Linux credentials, shell, or CAP_* on the vulnerable endpoint system.
- UI:NUser interaction, none
- Exploitation is fully automated once the attacker can submit concurrent DMA operations; no victim user action such as mounting filesystems or opening files is required.
- S:CScope, changed
- Corrupted shared DONE/ABORT masks and linked-list error enables on an endpoint can disrupt PCIe DMA to/from upstream host memory, impacting resources outside the endpoint kernel security authority across the PCIe boundary.
- C:LConfidentiality impact, low
- Lost interrupt unmasking can leave host-visible DMA buffers partially updated or stall reads, enabling limited cross-boundary disclosure of in-flight or stale data rather than arbitrary kernel memory read primitives.
- I:LIntegrity impact, low
- Register corruption can disable linked-list error detection and desynchronize DMA completion handling, causing limited unintended modification of host or device DMA buffers even though addresses are normally driver-controlled.
- A:HAvailability impact, high
- A lost DONE/ABORT unmask leaves channels permanently BUSY with completions never delivered, wedging dmaengine clients and endpoint services until reboot, constituting a severe availability failure.