Answer in brief
CVE-2026-43061 records a Unknown severity vulnerability in serial: 8250: Fix TX deadlock when using DMA. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=7c47e637dfadfbc691dd297b91d81ef939ca2080 <8190f9ab6ad90cb97652adbebd238b874a4ef70d || >=bf3f395b9c37956eca866c9e1679769ed7dcce68 <79a19bd936bb35f56ef0ccab1b3b59ebce8c762d || >=d470522c597b73e63cca04f3012aec28185113b7 <f76d91271bcacbd759a2e4ee3ea61faa6a727ccf || >=5e00346deb7bf40a4cf70e3716ac8e9a2409eb55 <d2719a0a9c3439abf67843a5504b7afccd9ded93 || >=c8a52c772c7c6de72257a435bcad03d3bb914a70 <2a72403b985aea6b4aac3171830492f9a387f9e1 || >=9e512eaaf8f4008c44ede3dfc0fbc9d9c5118583 <5f6b17562f03fc65c7d3474ef8f1959b19d1ca41 || >=9e512eaaf8f4008c44ede3dfc0fbc9d9c5118583 <b5ad887339503103d0fbe9827b16ad287597c275 || >=9e512eaaf8f4008c44ede3dfc0fbc9d9c5118583 <a424a34b8faddf97b5af41689087e7a230f79ba7 || bbec5998d7bd349730f59c959a8b00cfff816e34 || 59f751db7f392fa7a58cbd972205982f7f4f5854 || >=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 || >=5.4.291 <5.5 || >=6.13.4 <6.14 | 8190f9ab6ad90cb97652adbebd238b874a4ef70d, 79a19bd936bb35f56ef0ccab1b3b59ebce8c762d, f76d91271bcacbd759a2e4ee3ea61faa6a727ccf, d2719a0a9c3439abf67843a5504b7afccd9ded93, 2a72403b985aea6b4aac3171830492f9a387f9e1, 5f6b17562f03fc65c7d3474ef8f1959b19d1ca41, b5ad887339503103d0fbe9827b16ad287597c275, a424a34b8faddf97b5af41689087e7a230f79ba7, 5.10.253, 5.15.203, 6.1.167, 6.6.130, 6.12.78, 5.5, 6.14 |
| Linux/Linuxgeneric | 6.14 | Not reported |
Published upstream
May 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 6, 2026
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.
Quoted source text, attributed separately from HOL analysis.