CVE-2026-72146: dmaengine: sh: rz-dmac: Move interrupt request after everything is set up
Noroxi assessment
Priority: Monitor (action score 33/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.18% (FIRST EPSS).
- Someone with local access to the system 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 07ae600bd353b22f31a8f1007269744fafc7f123, 0e0c5b3cf374ebf3c589741751e1fbc67f53ec2f, 2a4d9e2234c3f817bb0ddbc8680d09ce9be84f93.
Low priority for now. Upgrade to Linux Linux 07ae600bd353b22f31a8f1007269744fafc7f123, 0e0c5b3cf374ebf3c589741751e1fbc67f53ec2f, 2a4d9e2234c3f817bb0ddbc8680d09ce9be84f93 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: sh: rz-dmac: Move interrupt request after everything is set up Once the interrupt is requested, the interrupt handler may run immediately. Since the IRQ handler can access channel->ch_base, which is initialized only after requesting the IRQ, this may lead to invalid memory access. Likewise, the IRQ thread may access uninitialized data (the ld_free, ld_queue, and ld_active lists), which may also lead to issues. Request the interrupts only after everything is set up. To keep the error path simpler, use dmam_alloc_coherent() instead of dma_alloc_coherent().
- Published
- Aug 15, 2026
- Updated
- Aug 19, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- —
Report tools
Action score
33
Monitor
Low priority for now.
- CVSS
- 33 / 40 · 8.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.4
- 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.15affected
- 5000d37042a61ca556fde2782ca40dbfa802ea16 and later · before d24d53323e817d79a4bd111bd10b34dbc96e64a8affected · git
- 5000d37042a61ca556fde2782ca40dbfa802ea16 and later · before 0e0c5b3cf374ebf3c589741751e1fbc67f53ec2faffected · git
- 5000d37042a61ca556fde2782ca40dbfa802ea16 and later · before 5b12de6229d662864ee22c11d4876652b40120f0affected · git
- 5000d37042a61ca556fde2782ca40dbfa802ea16 and later · before 2a4d9e2234c3f817bb0ddbc8680d09ce9be84f93affected · git
- 5000d37042a61ca556fde2782ca40dbfa802ea16 and later · before ec9f66c91bffdb69d309bae6dfb387562db7ebc8affected · git
- 5000d37042a61ca556fde2782ca40dbfa802ea16 and later · before 07ae600bd353b22f31a8f1007269744fafc7f123affected · git
- 5000d37042a61ca556fde2782ca40dbfa802ea16 and later · before 731712403ddb39d1a76a11abf339a0615bc85de7affected · git
- before 5.15not affected · semver
- 5.15.216 and later · up to and including 5.15.*not 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.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.101-1~deb12u1 | 6.12.101-1~deb12u1 |
| Debian:13 | linux | before 6.12.101-1 | 6.12.101-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-72142Aug 15, 2026 · i2c: imx: fix locked bus on SMBus block-read of 0 (atomic)0Monitor
- ← EarlierCVE-2026-72145Aug 15, 2026 · platform/x86/intel/tpmi: use cleanup helpers in mem_write()0Monitor
- Later →CVE-2026-72148Aug 15, 2026 · dmaengine: dw-edma: Add spinlock to protect DONE_INT_MASK and ABORT_INT_MASK35Monitor
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 | 07ae600bd353b22f31a8f1007269744fafc7f123 | Vendor (CNA) |
| Linux Linux | 0e0c5b3cf374ebf3c589741751e1fbc67f53ec2f | Vendor (CNA) |
| Linux Linux | 2a4d9e2234c3f817bb0ddbc8680d09ce9be84f93 | Vendor (CNA) |
| Linux Linux | 5b12de6229d662864ee22c11d4876652b40120f0 | Vendor (CNA) |
| Linux Linux | 731712403ddb39d1a76a11abf339a0615bc85de7 | Vendor (CNA) |
| Linux Linux | d24d53323e817d79a4bd111bd10b34dbc96e64a8 | Vendor (CNA) |
| Linux Linux | ec9f66c91bffdb69d309bae6dfb387562db7ebc8 | Vendor (CNA) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.101-1~deb12u1 · 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 with local access to the system 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
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 (6 more)Show less
- git.kernel.org/stable/c/0e0c5b3cf374ebf3c589741751e1fbc67f53ec2f
- git.kernel.org/stable/c/2a4d9e2234c3f817bb0ddbc8680d09ce9be84f93
- git.kernel.org/stable/c/5b12de6229d662864ee22c11d4876652b40120f0
- git.kernel.org/stable/c/731712403ddb39d1a76a11abf339a0615bc85de7
- git.kernel.org/stable/c/d24d53323e817d79a4bd111bd10b34dbc96e64a8
- git.kernel.org/stable/c/ec9f66c91bffdb69d309bae6dfb387562db7ebc8
Vendor advisories and official records. Exploit/PoC links are deliberately left out.