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-93040

dmaengine: dw-edma: Serialize channel state checks

Description

In the Linux kernel, the following vulnerability has been resolved: dmaengine: dw-edma: Serialize channel state checks pause() and resume() read and update channel state without holding vc.lock, while the interrupt handlers update the same state under it. Take the same lock around those state checks so that request, status, and configured stay consistent. For example, pause() can observe EDMA_ST_BUSY right before the interrupt handler completes the final descriptor and moves the channel to EDMA_ST_IDLE, and then record EDMA_REQ_PAUSE on an already idle channel. No further interrupt will acknowledge the request, and since issue_pending() requires EDMA_REQ_NONE, the channel is wedged for good: terminate_all() leaves the stale request behind, so even reconfiguring the channel does not recover it. issue_pending() already runs under vc.lock, but it tests configured before taking it. Move that test under the lock as well, so configured, request, and status are evaluated as one channel-state snapshot.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 32 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.22% · top 87% of all CVEs (11 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 e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf – < be0072af8ce6e9458cc586e0e8b41a251e7d4316
    • affected e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf – < 2d76b91deeab973dd8a8c2ee587ce27f881de768
    • affected e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf – < 3001cfcee30dcc81f8b3774319c12067f126e49a
    • affected e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf – < b6293a8a38f4d5866ce1a264c138265a02e4c53a
    • affected e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf – < da16a02f0998a0d455ce6265b836b29ad92e6e58
    • affected e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf – < fe0ffa0190e862ed71e8c1a476090f648c9cb7d9
    • affected e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf – < 6fc436e1500c5e4f0dde2a3dbadf6d898057be8f
    • affected e63d79d1ffcd2201a2dbff1d7a1184b8f3ec74cf – < f7d1619f3e10c619b62c6cd6d95371b5c526c85a
  • Linux · Linux

    • affected 5.3
    • unaffected < 5.3
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 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-93040 badge
[![CVE-2026-93040](https://cveledger.app/badge/CVE-2026-93040.svg)](https://cveledger.app/cve/CVE-2026-93040)

Record last updated .