Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-98344dmaengine: Fix device kref underflow in dma_chan_put()

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.

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 13 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.18% · top 93% of all CVEs (13 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 8ad342a863590b24ce77681b7e081363fb3333f7 – < 036b527f92570206da4b8c40b38f8d689e29d0f3
    • affected 8ad342a863590b24ce77681b7e081363fb3333f7 – < 5fb1797a8c9485e40e5492fa0338ab5c7d1f3fef
    • affected 8ad342a863590b24ce77681b7e081363fb3333f7 – < 57f7f1c6827be7d8f80feca48d2125fb91c6f6ed
    • affected 8ad342a863590b24ce77681b7e081363fb3333f7 – < 7c3f4ce651d43705f9ec7f778f642a90d5ff4fba
    • affected 8ad342a863590b24ce77681b7e081363fb3333f7 – < de2677e57d3161390d8a508f08cddec6ef7e4b23
    • affected 8ad342a863590b24ce77681b7e081363fb3333f7 – < 1a0d9b406febf23054ad595fd47b29325e70fb2d
    • affected 8ad342a863590b24ce77681b7e081363fb3333f7 – < 77906ac448d2fa81fa710ae26c0e591ebdc81154
    • affected 8ad342a863590b24ce77681b7e081363fb3333f7 – < 44dab659064eb5c10adb0306510eebe848ed592d
  • Linux · Linux

    • affected 5.6
    • unaffected < 5.6
    • unaffected 5.10.271 – ≤ 5.10.*
    • unaffected 5.15.222 – ≤ 5.15.*
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.112 – ≤ 6.12.*
    • unaffected 6.18.54 – ≤ 6.18.*
    • unaffected 7.2.8 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-98344 badge
[![CVE-2026-98344](https://cveledger.app/badge/CVE-2026-98344.svg)](https://cveledger.app/cve/CVE-2026-98344)

Record last updated .