CVE-2026-43061None▾ SunlitIn 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 t…
▾ Sunlit zone — Low / medium · no exploitation signal
impact 2.8 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake.
Exploit-prediction probability, daily snapshots since Nov 6.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
Last analysed / modified upstream
0.09%
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.
Linux >= 7c47e637dfadfbc691dd297b91d81ef939ca2080 < 8190f9ab6ad90cb97652adbebd238b874a4ef70dLinux >= bf3f395b9c37956eca866c9e1679769ed7dcce68 < 79a19bd936bb35f56ef0ccab1b3b59ebce8c762dLinux >= d470522c597b73e63cca04f3012aec28185113b7 < f76d91271bcacbd759a2e4ee3ea61faa6a727ccfLinux >= 5e00346deb7bf40a4cf70e3716ac8e9a2409eb55 < d2719a0a9c3439abf67843a5504b7afccd9ded93Linux >= c8a52c772c7c6de72257a435bcad03d3bb914a70 < 2a72403b985aea6b4aac3171830492f9a387f9e1Linux >= 9e512eaaf8f4008c44ede3dfc0fbc9d9c5118583 < 5f6b17562f03fc65c7d3474ef8f1959b19d1ca41Linux >= 9e512eaaf8f4008c44ede3dfc0fbc9d9c5118583 < b5ad887339503103d0fbe9827b16ad287597c275Linux >= 9e512eaaf8f4008c44ede3dfc0fbc9d9c5118583 < a424a34b8faddf97b5af41689087e7a230f79ba7Linux bbec5998d7bd349730f59c959a8b00cfff816e34Linux 59f751db7f392fa7a58cbd972205982f7f4f5854Linux >= 5.10.235 < 5.10.253Linux >= 5.15.179 < 5.15.203Linux >= 6.1.129 < 6.1.167Linux >= 6.6.79 < 6.6.130Linux >= 6.12.16 < 6.12.78Linux >= 5.4.291 < 5.5Linux >= 6.13.4 < 6.14Linux 6.14Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-99284Nonenet: skbuff: propagate shared-frag marker in skb_zerocopy()
CVE-2026-99283Nonenetfilter: conntrack: tcp: use UNACK timeout for non-closing RST packets
CVE-2026-99272Nonesmb: client: validate the data area in SMB2_read()
CVE-2026-99271NoneALSA: line6: Clear prev_fbuf on capture buffer release
CVE-2026-99273Noneksmbd: reserve space for the UTF-16 terminator in stream info
CVE-2026-99275Nonesmb: client: reject short SESSION_SETUP responses