CVE-2026-74654

serial: 8250_dma: Clear stale RX state on shutdown

N/A
Published: August 22, 2026 at 03:32 PM UTC
Updated: October 14, 2026 at 01:10 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

0fcb7901f9d61a325b4c5b88c600383bcbeb97fe3.19
Vendor states this is fixed in 9f2444f4c0e4b06f61bae38da87c9c94c78efa86 (fixed)
Vendor states this is fixed in ae05d9e50b6b9f246c110b3bdc03676145c2d0d4 (fixed)
Vendor states this is fixed in bf4fb620e02962b2b52500a4b3d8420f351eb46a (fixed)
Vendor states this is fixed in d06cfb1add4a2d5b393e9e31f49ebbd168beea49 (fixed)
Vendor states this is fixed in e10f06ee050a08930e2339b6fec7148fd0b2a8f6 (fixed)
Vendor states this is fixed in e2fe6a0efecbef00e3ecc2db64dd5afa8c212b41 (fixed)
Vendor states this is fixed in e7a5d792cf64a2096e18f1d573cc3d01cba15e92 (fixed)
Vendor states this is fixed in e7e3cc6709caa49d1d6ce6c1f7cb305e38675cc9 (fixed)
Vendor states this is fixed in 3.19 (unaffected)
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.104 (unaffected)
Vendor states this is fixed in 6.18.45 (unaffected)
Vendor states this is fixed in 6.6.152 (unaffected)
Vendor states this is fixed in 7.1.9 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card