CVE-2026-43061
Description
In the Linux kernel, the following vulnerability has been resolved: serial: 8250: Fix TX deadlock when using DMA `dmaengine_terminate_async` does not guarantee that the `__dma_tx_complete` callback will run. The callback is currently the only place where `dma->tx_running` gets cleared. If the transaction is canceled and the callback never runs, then `dma->tx_running` will never get cleared and we will never schedule new TX DMA transactions again. This change makes it so we clear `dma->tx_running` after we terminate the DMA transaction. This is "safe" because `serial8250_tx_dma_flush` is holding the UART port lock. The first thing the callback does is also grab the UART port lock, so access to `dma->tx_running` is serialized.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
OS impact
Linux kernel Affected 3 releases
| Version | Status | Fixed in |
|---|---|---|
| 7.0 | Affected | — |
| 6.14 | Affected | — |
| — | Affected | 5.5 |
SUSE Affected 1 release
| Version | Status | Fixed in |
|---|---|---|
| — | Affected | — |
Debian Fixed 5 releases
| Version | Status | Fixed in |
|---|---|---|
| trixie | Fixed | 6.12.85-1 |
| sid | Fixed | 6.19.10-1 |
| forky | Fixed | 6.19.10-1 |
| bullseye | Fixed | 5.10.257-1 |
| bookworm | Fixed | 6.1.170-1 |
References
- https://git.kernel.org/stable/c/2a72403b985aea6b4aac3171830492f9a387f9e1
- https://git.kernel.org/stable/c/5f6b17562f03fc65c7d3474ef8f1959b19d1ca41
- https://git.kernel.org/stable/c/79a19bd936bb35f56ef0ccab1b3b59ebce8c762d
- https://git.kernel.org/stable/c/8190f9ab6ad90cb97652adbebd238b874a4ef70d
- https://git.kernel.org/stable/c/a424a34b8faddf97b5af41689087e7a230f79ba7
- https://git.kernel.org/stable/c/b5ad887339503103d0fbe9827b16ad287597c275
- https://git.kernel.org/stable/c/d2719a0a9c3439abf67843a5504b7afccd9ded93
- https://git.kernel.org/stable/c/f76d91271bcacbd759a2e4ee3ea61faa6a727ccf
- https://www.suse.com/security/cve/CVE-2026-43061.html
- https://security-tracker.debian.org/tracker/CVE-2026-43061
CWEs
CWE-667
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.