CVE-2026-74654serial: 8250_dma: Clear stale RX state on shutdown
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- Not yet scored
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Aug 22, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from 0fcb7901f9d61a325b4c5b88c600383bcbeb97fe before bf4fb620e02962b2b52500a4b3d8420f351eb46a; from 0fcb7901f9d61a325b4c5b88c600383bcbeb97fe before e10f06ee050a08930e2339b6fec7148fd0b2a8f6; from 0fcb7901f9d61a325b4c5b88c600383bcbeb97fe before d06cfb1add4a2d5b393e9e31f49ebbd168beea49; from 0fcb7901f9d61a325b4c5b88c600383bcbeb97fe before e7a5d792cf64a2096e18f1d573cc3d01cba15e92; from 0fcb7901f9d61a325b4c5b88c600383bcbeb97fe before 9f2444f4c0e4b06f61bae38da87c9c94c78efa86; from 0fcb7901f9d61a325b4c5b88c600383bcbeb97fe before ae05d9e50b6b9f246c110b3bdc03676145c2d0d4; from 0fcb7901f9d61a325b4c5b88c600383bcbeb97fe before e7e3cc6709caa49d1d6ce6c1f7cb305e38675cc9; from 0fcb7901f9d61a325b4c5b88c600383bcbeb97fe before e2fe6a0efecbef00e3ecc2db64dd5afa8c212b41 | CNA record |
References
- https://git.kernel.org/stable/c/bf4fb620e02962b2b52500a4b3d8420f351eb46a
- https://git.kernel.org/stable/c/e10f06ee050a08930e2339b6fec7148fd0b2a8f6
- https://git.kernel.org/stable/c/d06cfb1add4a2d5b393e9e31f49ebbd168beea49
- https://git.kernel.org/stable/c/e7a5d792cf64a2096e18f1d573cc3d01cba15e92
- https://git.kernel.org/stable/c/9f2444f4c0e4b06f61bae38da87c9c94c78efa86
- https://git.kernel.org/stable/c/ae05d9e50b6b9f246c110b3bdc03676145c2d0d4
- https://git.kernel.org/stable/c/e7e3cc6709caa49d1d6ce6c1f7cb305e38675cc9
- https://git.kernel.org/stable/c/e2fe6a0efecbef00e3ecc2db64dd5afa8c212b41
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.