CVE-2026-74654 — serial: 8250_dma: Clear stale RX state on shutdown
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 0fcb7901f9d61a325b4c5b88c600383bcbeb97fe and < bf4fb620e02962b2b52500a4b3d8420f351eb46a≥ 0fcb7901f9d61a325b4c5b88c600383bcbeb97fe and < e10f06ee050a08930e2339b6fec7148fd0b2a8f6≥ 0fcb7901f9d61a325b4c5b88c600383bcbeb97fe and < d06cfb1add4a2d5b393e9e31f49ebbd168beea49≥ 0fcb7901f9d61a325b4c5b88c600383bcbeb97fe and < e7a5d792cf64a2096e18f1d573cc3d01cba15e92≥ 0fcb7901f9d61a325b4c5b88c600383bcbeb97fe and < 9f2444f4c0e4b06f61bae38da87c9c94c78efa86≥ 0fcb7901f9d61a325b4c5b88c600383bcbeb97fe and < ae05d9e50b6b9f246c110b3bdc03676145c2d0d4≥ 0fcb7901f9d61a325b4c5b88c600383bcbeb97fe and < e7e3cc6709caa49d1d6ce6c1f7cb305e38675cc9≥ 0fcb7901f9d61a325b4c5b88c600383bcbeb97fe and < e2fe6a0efecbef00e3ecc2db64dd5afa8c212b41 and 1 moreversion 3.19 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 14, 2026 – Oct 14, 2026
References
8 on the record
- git.kernel.org/stable/c/e2fe6a0efecbef00e3ecc2db64dd5afa8c212b41
- git.kernel.org/stable/c/e7a5d792cf64a2096e18f1d573cc3d01cba15e92
- git.kernel.org/stable/c/e10f06ee050a08930e2339b6fec7148fd0b2a8f6
- git.kernel.org/stable/c/bf4fb620e02962b2b52500a4b3d8420f351eb46a
- git.kernel.org/stable/c/d06cfb1add4a2d5b393e9e31f49ebbd168beea49
- git.kernel.org/stable/c/ae05d9e50b6b9f246c110b3bdc03676145c2d0d4
- git.kernel.org/stable/c/e7e3cc6709caa49d1d6ce6c1f7cb305e38675cc9
- git.kernel.org/stable/c/9f2444f4c0e4b06f61bae38da87c9c94c78efa86
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 8h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 8h
- Unknown CVE-2026-98428 ALSA: usb: 6fire: Avoid embedded URBs 1d
- Unknown CVE-2026-98430 RDMA/efa: Keep admin queues alive while IRQ is registered 1d
- Unknown CVE-2026-98429 RDMA/efa: Keep EQ resources alive while IRQ is registered 1d
- Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-74654 is "serial: 8250_dma: Clear stale RX state on shutdown", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.18% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.