CVE-2026-72148: dmaengine: dw-edma: Add spinlock to protect DONE_INT_MASK and ABORT_INT_MASK
Noroxi assessment
Priority: Monitor (action score 35/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.32% (FIRST EPSS).
- Someone on the same network segment can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 1553ca96e9df158d8f37137cf4bf5fb0dc981d94, 21a9834f56d6249aaa6ca7c2d8c182d66c48c3e1, 2247cc25a91fb1b5b86586ed55fdd5b725a7477c.
Low priority for now. Upgrade to Linux Linux 1553ca96e9df158d8f37137cf4bf5fb0dc981d94, 21a9834f56d6249aaa6ca7c2d8c182d66c48c3e1, 2247cc25a91fb1b5b86586ed55fdd5b725a7477c or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: dmaengine: dw-edma: Add spinlock to protect DONE_INT_MASK and ABORT_INT_MASK 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]
- Published
- Aug 15, 2026
- Updated
- Aug 23, 2026
- EPSS
- 0.3% · 25th percentile
- CWE
- —
Report tools
Action score
35
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.3affected
- 7e4b8a4fbe2cecab0959e862604803d063f50029 and later · before 3989b4775bc2cdbdb4ddc4b1d2420a82b40913f2affected · git
- 7e4b8a4fbe2cecab0959e862604803d063f50029 and later · before f60c7463d44fbc1585d247d0bd6976f7a1099472affected · git
- 7e4b8a4fbe2cecab0959e862604803d063f50029 and later · before 2247cc25a91fb1b5b86586ed55fdd5b725a7477caffected · git
- 7e4b8a4fbe2cecab0959e862604803d063f50029 and later · before 3ee0f478bb29b4ee892b178179a9a76ddd194149affected · git
- 7e4b8a4fbe2cecab0959e862604803d063f50029 and later · before 21a9834f56d6249aaa6ca7c2d8c182d66c48c3e1affected · git
- 7e4b8a4fbe2cecab0959e862604803d063f50029 and later · before ddbc4a8a4fe296f1fa2e59f7d176fc7c773df640affected · git
- 7e4b8a4fbe2cecab0959e862604803d063f50029 and later · before 1553ca96e9df158d8f37137cf4bf5fb0dc981d94affected · git
- 7e4b8a4fbe2cecab0959e862604803d063f50029 and later · before 8ffba0171c6bbce5f093c6dba5a02c0805b31203affected · git
- before 5.3not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.180-1 | 6.1.180-1 |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-72146Aug 15, 2026 · dmaengine: sh: rz-dmac: Move interrupt request after everything is set up33Monitor
- ← EarlierCVE-2026-72147Aug 15, 2026 · dmaengine: dw-edma-pcie: Reject devices without driver data0Monitor
- Later →CVE-2026-72150Aug 15, 2026 · sunrpc: fix uninitialized xprt_create_args structure0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1553ca96e9df158d8f37137cf4bf5fb0dc981d94 | Vendor (CNA) |
| Linux Linux | 21a9834f56d6249aaa6ca7c2d8c182d66c48c3e1 | Vendor (CNA) |
| Linux Linux | 2247cc25a91fb1b5b86586ed55fdd5b725a7477c | Vendor (CNA) |
| Linux Linux | 3989b4775bc2cdbdb4ddc4b1d2420a82b40913f2 | Vendor (CNA) |
| Linux Linux | 3ee0f478bb29b4ee892b178179a9a76ddd194149 | Vendor (CNA) |
| Linux Linux | 8ffba0171c6bbce5f093c6dba5a02c0805b31203 | Vendor (CNA) |
| Linux Linux | ddbc4a8a4fe296f1fa2e59f7d176fc7c773df640 | Vendor (CNA) |
| Linux Linux | f60c7463d44fbc1585d247d0bd6976f7a1099472 | Vendor (CNA) |
| debian:linux | 6.1.180-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone on the same network segment can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- high · the service can be disrupted
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Adjacent
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/21a9834f56d6249aaa6ca7c2d8c182d66c48c3e1
- git.kernel.org/stable/c/2247cc25a91fb1b5b86586ed55fdd5b725a7477c
- git.kernel.org/stable/c/3989b4775bc2cdbdb4ddc4b1d2420a82b40913f2
- git.kernel.org/stable/c/3ee0f478bb29b4ee892b178179a9a76ddd194149
- git.kernel.org/stable/c/8ffba0171c6bbce5f093c6dba5a02c0805b31203
- git.kernel.org/stable/c/ddbc4a8a4fe296f1fa2e59f7d176fc7c773df640
- git.kernel.org/stable/c/f60c7463d44fbc1585d247d0bd6976f7a1099472
Vendor advisories and official records. Exploit/PoC links are deliberately left out.