CVE-2026-98343
dmaengine: fix use-after-free in dma_chan_put() and dma_release_channel()
No known exploitation. EPSS puts it in the 7th percentile. Fixed versions are out.
What to do
Find your product and version, then upgrade to the build on the right.
- LinuxAffected: ≥ 8ad342a863590b24ce77681b7e081363fb3333f7, < b92c502595336a3cc5bb7a060170891366745a5dUpgrade to: b92c502595336a3cc5bb7a060170891366745a5dAffected: ≥ 8ad342a863590b24ce77681b7e081363fb3333f7, < 855187a88bdf762c46b6849307597e3e02bfc1d9Upgrade to: 855187a88bdf762c46b6849307597e3e02bfc1d9Affected: ≥ 8ad342a863590b24ce77681b7e081363fb3333f7, < c9780b601438137494b407eb4301bb3de2587ac9Upgrade to: c9780b601438137494b407eb4301bb3de2587ac9Affected: ≥ 8ad342a863590b24ce77681b7e081363fb3333f7, < 07eb075b60d565a5e465a1945a80cc62807492adUpgrade to: 07eb075b60d565a5e465a1945a80cc62807492ad + 4 more branchesStated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
In the Linux kernel, the following vulnerability has been resolved: dmaengine: fix use-after-free in dma_chan_put() and dma_release_channel() When dma_device_put() drops the last reference on chan->device->ref, dma_device_release() runs and may free the dma_device along with its channels. dma_chan_put() then still reads chan->device->owner via dma_chan_to_owner() for the trailing module_put(). KASAN catches it: slab-use-after-free in dma_chan_put+0x3e6/0x4c0 Read of size 8 by task insmod/6319 Freed by task 6319: kfree+0x225/0x470 dma_chan_put+0x395/0x4c0 dmaengine_put+0xf8/0x160 Cache the module owner in dma_chan_put() before the put so the trailing module_put() does not need chan->device.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.2% chance of exploitation activity in the next 30 days, which ranks it in the 7th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
2 events over 0 days, from the signal feeds we watch.
- Publishedrecord updated
Affected products
Sources
References in the record
- git.kernel.org/stable/c/b92c502595336a3cc5bb7a060170891366745a5d
- git.kernel.org/stable/c/855187a88bdf762c46b6849307597e3e02bfc1d9
- git.kernel.org/stable/c/c9780b601438137494b407eb4301bb3de2587ac9
And 5 more references. See all after sign-in
In the news
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Linux, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI