Serial transmission halt via uncleared DMA state
Published May 5, 2026 · Updated May 5, 2026
Improper locking in the 8250 UART DMA path in the Linux Kernel allows local users to halt serial transmission after a canceled transfer. serial8250_tx_dma_flush calls dmaengine_terminate_async but leaves dma->tx_running set when cancellation produces no __dma_tx_complete callback. Low-privileged local access and an affected 8250 UART using DMA are required; the stuck state prevents subsequent TX DMA scheduling and halts serial output.
Summary
What happened
Improper locking in the 8250 UART DMA path in the Linux Kernel allows local users to halt serial transmission after a canceled transfer. serial8250_tx_dma_flush calls dmaengine_terminate_async but leaves dma->tx_running set when cancellation produces no __dma_tx_complete callback. Low-privileged local access and an affected 8250 UART using DMA are required; the stuck state prevents subsequent TX DMA scheduling and halts serial output.
The record
- CVE
- CVE-2026-43061
- Published
- May 5, 2026
- Updated
- May 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-667, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 5, 2026CVE publishedPublication date reported by the CVE source.
- May 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=59f751db7f392fa7a58cbd972205982f7f4f5854
- Affected versionversion=5e00346deb7bf40a4cf70e3716ac8e9a2409eb55 <d2719a0a9c3439abf67843a5504b7afccd9ded93
- Affected versionversion=6.14
- Affected versionversion=7c47e637dfadfbc691dd297b91d81ef939ca2080 <8190f9ab6ad90cb97652adbebd238b874a4ef70d
- Affected versionversion=9e512eaaf8f4008c44ede3dfc0fbc9d9c5118583 <5f6b17562f03fc65c7d3474ef8f1959b19d1ca41
- Affected versionversion=9e512eaaf8f4008c44ede3dfc0fbc9d9c5118583 <a424a34b8faddf97b5af41689087e7a230f79ba7
- Affected versionversion=9e512eaaf8f4008c44ede3dfc0fbc9d9c5118583 <b5ad887339503103d0fbe9827b16ad287597c275
- Affected versionversion=bbec5998d7bd349730f59c959a8b00cfff816e34
- Affected versionversion=bf3f395b9c37956eca866c9e1679769ed7dcce68 <79a19bd936bb35f56ef0ccab1b3b59ebce8c762d
- Affected versionversion=c8a52c772c7c6de72257a435bcad03d3bb914a70 <2a72403b985aea6b4aac3171830492f9a387f9e1
- Affected versionversion=d470522c597b73e63cca04f3012aec28185113b7 <f76d91271bcacbd759a2e4ee3ea61faa6a727ccf
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo