CVE-2026-74654
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 versions
Linux kernel versions
3.19
and later are affected. Fixed in
5.10.265,
5.15.216,
6.1.183,
6.6.152,
6.12.104,
6.18.45,
7.1.9,
7.2
and their respective stable series.
References
8 totalFrequently asked questions
-
What is CVE-2026-74654?
CVE-2026-74654 is a unscored severity Linux kernel vulnerability . It affects Linux kernel versions from 3.19 onward and has been patched in 5.10.265, 5.15.216, 6.1.183 and others. CVE-2026-74654 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
Is there a patch available for CVE-2026-74654?
Yes. CVE-2026-74654 has been patched. Fixed versions include 5.10.265, 5.15.216, 6.1.183 and others. If you are running Linux kernel 3.19 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2026-74654 actively exploited?
No. CVE-2026-74654 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.