CVE-2026-98344

Unknown

Last modified

CVE-2026-98344 is a vulnerability of currently unknown severity. 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..

Description

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.

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 8ad342a863590b24ce77681b7e081363fb3333f7, < 036b527f92570206da4b8c40b38f8d689e29d0f3; >= 8ad342a863590b24ce77681b7e081363fb3333f7, < 5fb1797a8c9485e40e5492fa0338ab5c7d1f3fef; >= 8ad342a863590b24ce77681b7e081363fb3333f7, < 57f7f1c6827be7d8f80feca48d2125fb91c6f6ed; >= 8ad342a863590b24ce77681b7e081363fb3333f7, < 7c3f4ce651d43705f9ec7f778f642a90d5ff4fba; >= 8ad342a863590b24ce77681b7e081363fb3333f7, < de2677e57d3161390d8a508f08cddec6ef7e4b23; >= 8ad342a863590b24ce77681b7e081363fb3333f7, < 1a0d9b406febf23054ad595fd47b29325e70fb2d; >= 8ad342a863590b24ce77681b7e081363fb3333f7, < 77906ac448d2fa81fa710ae26c0e591ebdc81154; >= 8ad342a863590b24ce77681b7e081363fb3333f7, < 44dab659064eb5c10adb0306510eebe848ed592d
LinuxLinux5.6

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-98344?
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.
How severe is CVE-2026-98344?
Severity scoring for CVE-2026-98344 is pending analysis.
How do I fix CVE-2026-98344?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-98344?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST