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-98342dmaengine: wait for RCU readers before releasing dma_device

Description

In the Linux kernel, the following vulnerability has been resolved: dmaengine: wait for RCU readers before releasing dma_device dma_issue_pending_all() walks the dma_device_list with list_for_each_entry_rcu() under rcu_read_lock(). dma_device_release() unlinks the device with list_del_rcu() and then calls device->device_release() (which in many drivers, such as plx_dma.c, directly calls kfree()). Because there is no grace period between unlinking the device and freeing it, concurrent RCU readers in dma_issue_pending_all() can access the device after it has been freed. The lockless walk originally relied on clients holding a dmaengine reference to pin the provider module, and therefore the device, for as long as they might traverse the list. Commit 8ad342a86359 ("dmaengine: Add reference counting to dma_device struct") decoupled the dma_device lifetime from the module reference, so the device can now be released while a reader is still walking the list. Add synchronize_rcu() before the device is freed, so RCU readers are guaranteed to have finished. Keep it unconditional: providers that do not implement device_release() free the device themselves once dma_async_device_unregister() returns. This call will delay for a grace period with dma_list_mutex held, which is safe and only teardown path is delayed.

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 (12 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 2ba05622b8b143b0c95968ba59bddfbd6d2f2559 – < ac8ce9f89638d6d79875cca7d8ae42566a9bde15
    • affected 2ba05622b8b143b0c95968ba59bddfbd6d2f2559 – < 14578c78405d51fa92e4ada4502a45f537c0fcb8
    • affected 2ba05622b8b143b0c95968ba59bddfbd6d2f2559 – < cbb3310a5167e868a5e763e32b9a23b4d50669ee
    • affected 2ba05622b8b143b0c95968ba59bddfbd6d2f2559 – < 8577a5ec4f7e00443015ef99f646def093121a1b
    • affected 2ba05622b8b143b0c95968ba59bddfbd6d2f2559 – < 4448a539a0c39141cccc67be6cacde0f35024313
    • affected 2ba05622b8b143b0c95968ba59bddfbd6d2f2559 – < fc1f4884f1d46fc7a8cee6e2997ecc9e8d1c7f77
    • affected 2ba05622b8b143b0c95968ba59bddfbd6d2f2559 – < 4aed7e47a10b94ea3c5171e8d1382081accd2e03
    • affected 2ba05622b8b143b0c95968ba59bddfbd6d2f2559 – < dc750422170a563c7a81f6e49d36bb02c62ae37f
  • Linux · Linux

    • affected 2.6.29
    • unaffected < 2.6.29
    • 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-98342 badge
[![CVE-2026-98342](https://cveledger.app/badge/CVE-2026-98342.svg)](https://cveledger.app/cve/CVE-2026-98342)

Record last updated .