CVE-2026-43061 Details
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.
A vulnerability in the Linux kernel's 8250 serial driver can lead to a deadlock in transmitting data over Direct Memory Access (DMA). This issue arises because the function 'dmaengine_terminate_async' does not ensure that the '__dma_tx_complete' callback is executed. The callback is crucial as it clears the 'tx_running' status of the DMA transaction. If the callback is skipped, the 'tx_running' flag remains set, preventing the scheduling of new DMA transmissions, which can disrupt data flow and cause communication issues.
The vulnerability has been addressed in the Linux kernel. Users should upgrade to the latest version where this issue has been fixed.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/2a72403b985aea6b4aac3171830492f9a387f9e1 | kernel.org | Patch |
| https://git.kernel.org/stable/c/5f6b17562f03fc65c7d3474ef8f1959b19d1ca41 | kernel.org | Patch |
| https://git.kernel.org/stable/c/79a19bd936bb35f56ef0ccab1b3b59ebce8c762d | kernel.org | Patch |
| https://git.kernel.org/stable/c/8190f9ab6ad90cb97652adbebd238b874a4ef70d | kernel.org | Patch |
| https://git.kernel.org/stable/c/a424a34b8faddf97b5af41689087e7a230f79ba7 | kernel.org | Patch |
| https://git.kernel.org/stable/c/b5ad887339503103d0fbe9827b16ad287597c275 | kernel.org | Patch |
| https://git.kernel.org/stable/c/d2719a0a9c3439abf67843a5504b7afccd9ded93 | kernel.org | Patch |
| https://git.kernel.org/stable/c/f76d91271bcacbd759a2e4ee3ea61faa6a727ccf | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-667 | Improper Locking | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 5.4.291, < 5.5 >= 5.10.235, < 5.10.253 >= 5.15.179, < 5.15.203 >= 6.1.129, < 6.1.167 >= 6.6.79, < 6.6.130 >= 6.12.16, < 6.12.78 >= 6.13.4, < 6.14 >= 6.14.1, < 6.18.20 >= 6.19, < 6.19.10 6.14 - 6.14 rc3 6.14 rc4 6.14 rc5 6.14 rc6 6.14 rc7 7.0 rc1 7.0 rc2 7.0 rc3 7.0 rc4 7.0 rc5 7.0 rc6 7.0 rc7 |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| May 29, 2026 | Initial Analysis | [email protected] |
| May 5, 2026 | New CVE Received | kernel.org |