CVE-2026-72474: dmaengine: dma-axi-dmac: use DMA pool to manange DMA descriptor
Noroxi assessment
Priority: Monitor (action score 0/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.20% (FIRST EPSS).
- Fixed version: Linux Linux 65e82fa24965b2eb6ad9412f6c530ed9a50a625f, 9e942c8579130e62734c14338e9f451780669164, a4f41ceecfe68e117bae9c76c5ebc5e2b353fa56.
Low priority for now. Upgrade to Linux Linux 65e82fa24965b2eb6ad9412f6c530ed9a50a625f, 9e942c8579130e62734c14338e9f451780669164, a4f41ceecfe68e117bae9c76c5ebc5e2b353fa56 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: dma-axi-dmac: use DMA pool to manange DMA descriptor For architectures like Microblaze or arm64 (where this IP is used), DMA_DIRECT_REMAP is set which means that dma_alloc_coherent() might remap (and hence vmalloc()) some memory. This became visible in a design where dma_direct_use_pool() is not possible. With the above, when calling dma_free_coherent(), vunmap() would be called from softirq context and thus leading to a BUG(). To fix it, use a dma pool that is allocated in .device_alloc_chan_resources() and allocate blocks from it. The key point is that now dma_pool_free() is used in axi_dmac_free_desc() to free the blocks and that just frees the blocks from the pool in the sense they can be used again. In other words, no actual call to dma_free_coherent() happens. That only happens when destroying the pool in axi_dmac_free_chan_resources() which does not happen in any interrupt context.
- Published
- Aug 15, 2026
- Updated
- Aug 17, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
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.
Is your version affected? Check itNoroxi 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
- 6.8affected
- 3f8fd25936ee5f52596f10d420f650c5b5e3285f and later · before a4f41ceecfe68e117bae9c76c5ebc5e2b353fa56affected · git
- 3f8fd25936ee5f52596f10d420f650c5b5e3285f and later · before c0e6bb2b0408fcac6382158ee2bd9fdc45eceee9affected · git
- 3f8fd25936ee5f52596f10d420f650c5b5e3285f and later · before 65e82fa24965b2eb6ad9412f6c530ed9a50a625faffected · git
- 3f8fd25936ee5f52596f10d420f650c5b5e3285f and later · before 9e942c8579130e62734c14338e9f451780669164affected · git
- before 6.8not affected · semver
- 6.12.97 and later · up to and including 6.12.*not affected · semver
- 6.18.40 and later · up to and including 6.18.*not affected · semver
- 7.1.5 and later · up to and including 7.1.*not affected · semver
- 7.2 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| 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-72468Aug 15, 2026 · xprtrdma: Initialize re_id before removal registration0Monitor
- ← EarlierCVE-2026-72471Aug 15, 2026 · fs/ntfs3: prevent potential lcn remains uninitialized28Monitor
- Later →CVE-2026-72475Aug 15, 2026 · dmaengine: dma-axi-dmac: Properly free struct axi_dmac_desc0Monitor
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 | 65e82fa24965b2eb6ad9412f6c530ed9a50a625f | Vendor (CNA) |
| Linux Linux | 9e942c8579130e62734c14338e9f451780669164 | Vendor (CNA) |
| Linux Linux | a4f41ceecfe68e117bae9c76c5ebc5e2b353fa56 | Vendor (CNA) |
| Linux Linux | c0e6bb2b0408fcac6382158ee2bd9fdc45eceee9 | Vendor (CNA) |
| debian:linux | 6.12.100-1 · Debian:13 | 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).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
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 (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.