CVE-2026-74654

published 22 Aug 2026 · updated 20 Nov 2026

serial: 8250_dma: Clear stale RX state on shutdown

5.5MediumCVSS 5.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel e7e3cc6709caa49d1d6ce6c1f7cb305e38675cc9, Kernel 9f2444f4c0e4b06f61bae38da87c9c94c78efa86, Kernel ae05d9e50b6b9f246c110b3bdc03676145c2d0d4 and 12 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=0fcb7901f9d61a325b4c5b88c600383bcbeb97fe <e7e3cc6709caa49d1d6ce6c1f7cb305e38675cc9, >=0fcb7901f9d61a325b4c5b88c600383bcbeb97fe <9f2444f4c0e4b06f61bae38da87c9c94c78efa86, >=0fcb7901f9d61a325b4c5b88c600383bcbeb97fe <ae05d9e50b6b9f246c110b3bdc03676145c2d0d4, >=0fcb7901f9d61a325b4c5b88c600383bcbeb97fe <bf4fb620e02962b2b52500a4b3d8420f351eb46a, >=0fcb7901f9d61a325b4c5b88c600383bcbeb97fe <d06cfb1add4a2d5b393e9e31f49ebbd168beea49, >=0fcb7901f9d61a325b4c5b88c600383bcbeb97fe <e10f06ee050a08930e2339b6fec7148fd0b2a8f6, >=0fcb7901f9d61a325b4c5b88c600383bcbeb97fe <e2fe6a0efecbef00e3ecc2db64dd5afa8c212b41, >=0fcb7901f9d61a325b4c5b88c600383bcbeb97fe <e7a5d792cf64a2096e18f1d573cc3d01cba15e92, =3.19e7e3cc6709caa49d1d6ce6c1f7cb305e38675cc9, 9f2444f4c0e4b06f61bae38da87c9c94c78efa86, ae05d9e50b6b9f246c110b3bdc03676145c2d0d4, bf4fb620e02962b2b52500a4b3d8420f351eb46a, d06cfb1add4a2d5b393e9e31f49ebbd168beea49, e10f06ee050a08930e2339b6fec7148fd0b2a8f6, e2fe6a0efecbef00e3ecc2db64dd5afa8c212b41, e7a5d792cf64a2096e18f1d573cc3d01cba15e92
linux-kernel: Kernel>=5.11.0 <5.15.216, >=5.16.0 <6.1.183, >=6.13.0 <6.18.45, >=6.19.0 <7.1.9, >=6.2.0 <6.6.152, >=6.7.0 <6.12.104, >=3.19.0 <5.10.2655.15.216, 6.1.183, 6.18.45, 7.1.9, 6.6.152, 6.12.104, 5.10.265

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-74654 severity on Zeptric[![CVE-2026-74654](https://zeptric.io/badge/cve/CVE-2026-74654.svg)](https://zeptric.io/cve/CVE-2026-74654)