CVE-2026-74654: serial: 8250_dma: Clear stale RX state on shutdown
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Fixed version: Linux Linux 9f2444f4c0e4b06f61bae38da87c9c94c78efa86, ae05d9e50b6b9f246c110b3bdc03676145c2d0d4, bf4fb620e02962b2b52500a4b3d8420f351eb46a; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 6.6.152.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 9f2444f4c0e4b06f61bae38da87c9c94c78efa86, ae05d9e50b6b9f246c110b3bdc03676145c2d0d4, bf4fb620e02962b2b52500a4b3d8420f351eb46a; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 6.6.152.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 22, 2026
- Updated
- Nov 6, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 3.19affected
- 0fcb7901f9d61a325b4c5b88c600383bcbeb97fe and later · before bf4fb620e02962b2b52500a4b3d8420f351eb46aaffected · git
- 0fcb7901f9d61a325b4c5b88c600383bcbeb97fe and later · before e10f06ee050a08930e2339b6fec7148fd0b2a8f6affected · git
- 0fcb7901f9d61a325b4c5b88c600383bcbeb97fe and later · before d06cfb1add4a2d5b393e9e31f49ebbd168beea49affected · git
- 0fcb7901f9d61a325b4c5b88c600383bcbeb97fe and later · before e7a5d792cf64a2096e18f1d573cc3d01cba15e92affected · git
- 0fcb7901f9d61a325b4c5b88c600383bcbeb97fe and later · before 9f2444f4c0e4b06f61bae38da87c9c94c78efa86affected · git
- 0fcb7901f9d61a325b4c5b88c600383bcbeb97fe and later · before ae05d9e50b6b9f246c110b3bdc03676145c2d0d4affected · git
- 0fcb7901f9d61a325b4c5b88c600383bcbeb97fe and later · before e7e3cc6709caa49d1d6ce6c1f7cb305e38675cc9affected · git
- 0fcb7901f9d61a325b4c5b88c600383bcbeb97fe and later · before e2fe6a0efecbef00e3ecc2db64dd5afa8c212b41affected · git
- before 3.19not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.107-1~deb12u1 | 6.12.107-1~deb12u1 |
| Debian:13 | linux | before 6.12.105-1 | 6.12.105-1 |
| Debian:14 | linux | before 7.1.9-1 | 7.1.9-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-74652Aug 22, 2026 · serial: amba-pl011: cancel RS485 hrtimers after freeing IRQ31Monitor
- ← EarlierCVE-2026-74653Aug 22, 2026 · serial: 8250_of: clear stuck empty-FIFO RX-timeout on LPC32xx0Monitor
- Later →CVE-2026-74655Aug 22, 2026 · serial: qcom-geni: fix TX DMA buffer flush35Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 9f2444f4c0e4b06f61bae38da87c9c94c78efa86 | Vendor (CNA) |
| Linux Linux | ae05d9e50b6b9f246c110b3bdc03676145c2d0d4 | Vendor (CNA) |
| Linux Linux | bf4fb620e02962b2b52500a4b3d8420f351eb46a | Vendor (CNA) |
| Linux Linux | d06cfb1add4a2d5b393e9e31f49ebbd168beea49 | Vendor (CNA) |
| Linux Linux | e10f06ee050a08930e2339b6fec7148fd0b2a8f6 | Vendor (CNA) |
| Linux Linux | e2fe6a0efecbef00e3ecc2db64dd5afa8c212b41 | Vendor (CNA) |
| Linux Linux | e7a5d792cf64a2096e18f1d573cc3d01cba15e92 | Vendor (CNA) |
| Linux Linux | e7e3cc6709caa49d1d6ce6c1f7cb305e38675cc9 | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | 6.6.152.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.107-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0893 · Aug 24, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/ae05d9e50b6b9f246c110b3bdc03676145c2d0d4
- git.kernel.org/stable/c/bf4fb620e02962b2b52500a4b3d8420f351eb46a
- git.kernel.org/stable/c/d06cfb1add4a2d5b393e9e31f49ebbd168beea49
- git.kernel.org/stable/c/e10f06ee050a08930e2339b6fec7148fd0b2a8f6
- git.kernel.org/stable/c/e2fe6a0efecbef00e3ecc2db64dd5afa8c212b41
- git.kernel.org/stable/c/e7a5d792cf64a2096e18f1d573cc3d01cba15e92
- git.kernel.org/stable/c/e7e3cc6709caa49d1d6ce6c1f7cb305e38675cc9
Vendor advisories and official records. Exploit/PoC links are deliberately left out.