CVE-2026-43061
serial: 8250: Fix TX deadlock when using DMA
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.
INFO
Published Date :
May 5, 2026, 4:16 p.m.
Last Modified :
May 29, 2026, 6:24 p.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | MEDIUM | [email protected] |
Solution
- Update the Linux kernel.
- Apply the provided patch.
- Clear tx_running after terminating DMA.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-43061.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-43061 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-43061
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-43061 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-43061 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
Initial Analysis by [email protected]
May. 29, 2026
Action Type Old Value New Value Added CVSS V3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Added CWE CWE-667 Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:6.14:rc3:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:6.14:rc4:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:6.14:rc5:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:6.14:rc6:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:6.14:rc7:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:6.14:-:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.0:rc1:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.0:rc2:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.0:rc3:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.0:rc4:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.0:rc5:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.0:rc6:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.0:rc7:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.19 up to (excluding) 6.19.10 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.14.1 up to (excluding) 6.18.20 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.10.235 up to (excluding) 5.10.253 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.15.179 up to (excluding) 5.15.203 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.4.291 up to (excluding) 5.5 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.1.129 up to (excluding) 6.1.167 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.12.16 up to (excluding) 6.12.78 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.13.4 up to (excluding) 6.14 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.6.79 up to (excluding) 6.6.130 Added Reference Type kernel.org: https://git.kernel.org/stable/c/2a72403b985aea6b4aac3171830492f9a387f9e1 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/5f6b17562f03fc65c7d3474ef8f1959b19d1ca41 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/79a19bd936bb35f56ef0ccab1b3b59ebce8c762d Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/8190f9ab6ad90cb97652adbebd238b874a4ef70d Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/a424a34b8faddf97b5af41689087e7a230f79ba7 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/b5ad887339503103d0fbe9827b16ad287597c275 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/d2719a0a9c3439abf67843a5504b7afccd9ded93 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/f76d91271bcacbd759a2e4ee3ea61faa6a727ccf Types: Patch -
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
May. 05, 2026
Action Type Old Value New Value Added 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. Added Reference https://git.kernel.org/stable/c/2a72403b985aea6b4aac3171830492f9a387f9e1 Added Reference https://git.kernel.org/stable/c/5f6b17562f03fc65c7d3474ef8f1959b19d1ca41 Added Reference https://git.kernel.org/stable/c/79a19bd936bb35f56ef0ccab1b3b59ebce8c762d Added Reference https://git.kernel.org/stable/c/8190f9ab6ad90cb97652adbebd238b874a4ef70d Added Reference https://git.kernel.org/stable/c/a424a34b8faddf97b5af41689087e7a230f79ba7 Added Reference https://git.kernel.org/stable/c/b5ad887339503103d0fbe9827b16ad287597c275 Added Reference https://git.kernel.org/stable/c/d2719a0a9c3439abf67843a5504b7afccd9ded93 Added Reference https://git.kernel.org/stable/c/f76d91271bcacbd759a2e4ee3ea61faa6a727ccf