CVE-2026-98344: dmaengine: Fix device kref underflow in dma_chan_put()
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.17% (FIRST EPSS).
- Fixed version: Linux Linux 036b527f92570206da4b8c40b38f8d689e29d0f3, 1a0d9b406febf23054ad595fd47b29325e70fb2d, 44dab659064eb5c10adb0306510eebe848ed592d; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1.
Low priority for now. Upgrade to Linux Linux 036b527f92570206da4b8c40b38f8d689e29d0f3, 1a0d9b406febf23054ad595fd47b29325e70fb2d, 44dab659064eb5c10adb0306510eebe848ed592d; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1 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: Fix device kref underflow in dma_chan_put() dma_chan_get() takes chan->device->ref only on the slow path: /* no kref on fast path */ if (chan->client_count) { __module_get(owner); chan->client_count++; return 0; } if (!try_module_get(owner)) return -ENODEV; if (!dma_device_get(chan->device)) { // calls kref_get_unless_zero() dma_chan_put() drops the ref unconditionally, so every fast-path get/put pair drops one extra device reference. The bug fires when two conditions hold together: a non-private provider has a persistent client holding chan->client_count > 0 and another client cycles dmaengine_get()/dmaengine_put(). When the kref hits zero, the subsequent dma_find_channel() returns NULL even though the provider module is still loaded. Fix this by dropping device->ref only on the last put, matching the single slow-path get.
- Published
- Oct 6, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
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
- 5.6affected
- 8ad342a863590b24ce77681b7e081363fb3333f7 and later · before 036b527f92570206da4b8c40b38f8d689e29d0f3affected · git
- 8ad342a863590b24ce77681b7e081363fb3333f7 and later · before 5fb1797a8c9485e40e5492fa0338ab5c7d1f3fefaffected · git
- 8ad342a863590b24ce77681b7e081363fb3333f7 and later · before 57f7f1c6827be7d8f80feca48d2125fb91c6f6edaffected · git
- 8ad342a863590b24ce77681b7e081363fb3333f7 and later · before 7c3f4ce651d43705f9ec7f778f642a90d5ff4fbaaffected · git
- 8ad342a863590b24ce77681b7e081363fb3333f7 and later · before de2677e57d3161390d8a508f08cddec6ef7e4b23affected · git
- 8ad342a863590b24ce77681b7e081363fb3333f7 and later · before 1a0d9b406febf23054ad595fd47b29325e70fb2daffected · git
- 8ad342a863590b24ce77681b7e081363fb3333f7 and later · before 77906ac448d2fa81fa710ae26c0e591ebdc81154affected · git
- 8ad342a863590b24ce77681b7e081363fb3333f7 and later · before 44dab659064eb5c10adb0306510eebe848ed592daffected · git
- before 5.6not 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.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.113-1~deb12u1 | 6.12.113-1~deb12u1 |
| Debian:13 | linux | before 6.12.113-1 | 6.12.113-1 |
| Debian:14 | linux | before 7.2.8-1 | 7.2.8-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-98342Oct 6, 2026 · dmaengine: wait for RCU readers before releasing dma_device0Monitor
- ← EarlierCVE-2026-98343Oct 6, 2026 · dmaengine: fix use-after-free in dma_chan_put() and dma_release_channel()0Monitor
- Later →CVE-2026-98345Oct 6, 2026 · wifi: cfg80211: check IP header size in cfg80211_classify8021d()0Monitor
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 | 036b527f92570206da4b8c40b38f8d689e29d0f3 | Vendor (CNA) |
| Linux Linux | 1a0d9b406febf23054ad595fd47b29325e70fb2d | Vendor (CNA) |
| Linux Linux | 44dab659064eb5c10adb0306510eebe848ed592d | Vendor (CNA) |
| Linux Linux | 57f7f1c6827be7d8f80feca48d2125fb91c6f6ed | Vendor (CNA) |
| Linux Linux | 5fb1797a8c9485e40e5492fa0338ab5c7d1f3fef | Vendor (CNA) |
| Linux Linux | 77906ac448d2fa81fa710ae26c0e591ebdc81154 | Vendor (CNA) |
| Linux Linux | 7c3f4ce651d43705f9ec7f778f642a90d5ff4fba | Vendor (CNA) |
| Linux Linux | de2677e57d3161390d8a508f08cddec6ef7e4b23 | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | 6.6.158.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.113-1 · Debian:13 | Package registry (OSV) |
| debian:linux | 7.2.8-1 · Debian:14 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.113-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.
- Published
- Fix recordedsame day
- TodayNov 11, 2026+36 d
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
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
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/1a0d9b406febf23054ad595fd47b29325e70fb2d
- git.kernel.org/stable/c/44dab659064eb5c10adb0306510eebe848ed592d
- git.kernel.org/stable/c/57f7f1c6827be7d8f80feca48d2125fb91c6f6ed
- git.kernel.org/stable/c/5fb1797a8c9485e40e5492fa0338ab5c7d1f3fef
- git.kernel.org/stable/c/77906ac448d2fa81fa710ae26c0e591ebdc81154
- git.kernel.org/stable/c/7c3f4ce651d43705f9ec7f778f642a90d5ff4fba
- git.kernel.org/stable/c/de2677e57d3161390d8a508f08cddec6ef7e4b23
Vendor advisories and official records. Exploit/PoC links are deliberately left out.