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-74654serial: 8250_dma: Clear stale RX state on shutdown

Description

In the Linux kernel, the following vulnerability has been resolved: serial: 8250_dma: Clear stale RX state on shutdown serial8250_release_dma() terminates RX DMA and releases the channel, but leaves rx_running set. If the port is closed while an RX transfer is active, the stale state remains while rxchan is NULL until the channel is requested again on the next open. The DesignWare BUSY workaround added by commit a7b9ce39fbe4 ("serial: 8250_dw: Ensure BUSY is deasserted") calls serial8250_rx_dma_flush() from the LCR write path during startup. This happens before serial8250_request_dma() obtains a new RX channel. On reopen, the stale rx_running state therefore makes the flush path pass a NULL channel to dmaengine_pause(), causing a kernel Oops. Clear rx_running after terminating RX DMA, matching the TX cleanup. Also make the flush helper return if the DMA object or RX channel is not available so startup and teardown paths cannot pass a NULL channel to the DMAengine API.

Timeline

  1. ID reserved

    By Linux

  2. · 7 days later

    Published

  3. · 3 months 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 (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
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 0fcb7901f9d61a325b4c5b88c600383bcbeb97fe – < bf4fb620e02962b2b52500a4b3d8420f351eb46a
    • affected 0fcb7901f9d61a325b4c5b88c600383bcbeb97fe – < e10f06ee050a08930e2339b6fec7148fd0b2a8f6
    • affected 0fcb7901f9d61a325b4c5b88c600383bcbeb97fe – < d06cfb1add4a2d5b393e9e31f49ebbd168beea49
    • affected 0fcb7901f9d61a325b4c5b88c600383bcbeb97fe – < e7a5d792cf64a2096e18f1d573cc3d01cba15e92
    • affected 0fcb7901f9d61a325b4c5b88c600383bcbeb97fe – < 9f2444f4c0e4b06f61bae38da87c9c94c78efa86
    • affected 0fcb7901f9d61a325b4c5b88c600383bcbeb97fe – < ae05d9e50b6b9f246c110b3bdc03676145c2d0d4
    • affected 0fcb7901f9d61a325b4c5b88c600383bcbeb97fe – < e7e3cc6709caa49d1d6ce6c1f7cb305e38675cc9
    • affected 0fcb7901f9d61a325b4c5b88c600383bcbeb97fe – < e2fe6a0efecbef00e3ecc2db64dd5afa8c212b41
  • Linux · Linux

    • affected 3.19
    • unaffected < 3.19
    • unaffected 5.10.265 – ≤ 5.10.*
    • unaffected 5.15.216 – ≤ 5.15.*
    • unaffected 6.1.183 – ≤ 6.1.*
    • unaffected 6.6.152 – ≤ 6.6.*
    • unaffected 6.12.104 – ≤ 6.12.*
    • unaffected 6.18.45 – ≤ 6.18.*
    • unaffected 7.1.9 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .