CVE-2026-74654: Linux kernel · serial: 8250_dma: Clear stale RX state on shutdown
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in e10f06ee050a08930e2339b6fec7148fd0b2a8f6 : update Linux kernel when convenient.
Data as of 6 Nov 2026, 17:48 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-06.
- Patch
- Available – fixed in e10f06ee050a08930e2339b6fec7148fd0b2a8f6, e7e3cc6709caa49d1d6ce6c1f7cb305e38675cc9, e7a5d792cf64a2096e18f1d573cc3d01cba15e92 +5
Exploitation evidence
Disclosed: evidence found.
CVE published 22 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix is available and has been applied in the Linux kernel. Users should update to a fixed kernel version containing the patches identified by the provided commit hashes. No additional mitigation is required once the kernel is updated.
Description
A vulnerability in the Linux kernel serial driver (8250_dma) causes stale RX state to remain set after RX DMA termination during port shutdown. This stale state can lead to a kernel Oops when reopening the port due to a NULL channel passed to the DMA engine API. The issue has been fixed by clearing the rx_running flag after terminating RX DMA and improving flush helper behavior to avoid NULL channel usage.
References
- git.kernel.org/stable/c/bf4fb620e02962b2b52500a4b3d8420f351eb46a (opens in a new tab)
- git.kernel.org/stable/c/e10f06ee050a08930e2339b6fec7148fd0b2a8f6 (opens in a new tab)
- git.kernel.org/stable/c/d06cfb1add4a2d5b393e9e31f49ebbd168beea49 (opens in a new tab)
- git.kernel.org/stable/c/e7a5d792cf64a2096e18f1d573cc3d01cba15e92 (opens in a new tab)
- git.kernel.org/stable/c/9f2444f4c0e4b06f61bae38da87c9c94c78efa86 (opens in a new tab)
- git.kernel.org/stable/c/ae05d9e50b6b9f246c110b3bdc03676145c2d0d4 (opens in a new tab)
- git.kernel.org/stable/c/e7e3cc6709caa49d1d6ce6c1f7cb305e38675cc9 (opens in a new tab)
- git.kernel.org/stable/c/e2fe6a0efecbef00e3ecc2db64dd5afa8c212b41 (opens in a new tab)