Answer in brief
CVE-2026-74654 records a Unknown severity vulnerability in serial: 8250_dma: Clear stale RX state on shutdown. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=0fcb7901f9d61a325b4c5b88c600383bcbeb97fe <bf4fb620e02962b2b52500a4b3d8420f351eb46a || >=0fcb7901f9d61a325b4c5b88c600383bcbeb97fe <e10f06ee050a08930e2339b6fec7148fd0b2a8f6 || >=0fcb7901f9d61a325b4c5b88c600383bcbeb97fe <d06cfb1add4a2d5b393e9e31f49ebbd168beea49 || >=0fcb7901f9d61a325b4c5b88c600383bcbeb97fe <e7a5d792cf64a2096e18f1d573cc3d01cba15e92 || >=0fcb7901f9d61a325b4c5b88c600383bcbeb97fe <9f2444f4c0e4b06f61bae38da87c9c94c78efa86 || >=0fcb7901f9d61a325b4c5b88c600383bcbeb97fe <ae05d9e50b6b9f246c110b3bdc03676145c2d0d4 || >=0fcb7901f9d61a325b4c5b88c600383bcbeb97fe <e7e3cc6709caa49d1d6ce6c1f7cb305e38675cc9 || >=0fcb7901f9d61a325b4c5b88c600383bcbeb97fe <e2fe6a0efecbef00e3ecc2db64dd5afa8c212b41 | bf4fb620e02962b2b52500a4b3d8420f351eb46a, e10f06ee050a08930e2339b6fec7148fd0b2a8f6, d06cfb1add4a2d5b393e9e31f49ebbd168beea49, e7a5d792cf64a2096e18f1d573cc3d01cba15e92, 9f2444f4c0e4b06f61bae38da87c9c94c78efa86, ae05d9e50b6b9f246c110b3bdc03676145c2d0d4, e7e3cc6709caa49d1d6ce6c1f7cb305e38675cc9, e2fe6a0efecbef00e3ecc2db64dd5afa8c212b41 |
| Linux/Linuxgeneric | 3.19 | Not reported |
Published upstream
Aug 22, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 22, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 22, 2026
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.
Quoted source text, attributed separately from HOL analysis.