Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-43061serial: 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.

Timeline

  1. ID reserved

    By Linux

  2. · 4 days later

    Published

  3. · 6 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-43061, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.09% · top 100% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 7c47e637dfadfbc691dd297b91d81ef939ca2080 – < 8190f9ab6ad90cb97652adbebd238b874a4ef70d
    • affected bf3f395b9c37956eca866c9e1679769ed7dcce68 – < 79a19bd936bb35f56ef0ccab1b3b59ebce8c762d
    • affected d470522c597b73e63cca04f3012aec28185113b7 – < f76d91271bcacbd759a2e4ee3ea61faa6a727ccf
    • affected 5e00346deb7bf40a4cf70e3716ac8e9a2409eb55 – < d2719a0a9c3439abf67843a5504b7afccd9ded93
    • affected c8a52c772c7c6de72257a435bcad03d3bb914a70 – < 2a72403b985aea6b4aac3171830492f9a387f9e1
    • affected 9e512eaaf8f4008c44ede3dfc0fbc9d9c5118583 – < 5f6b17562f03fc65c7d3474ef8f1959b19d1ca41
    • affected 9e512eaaf8f4008c44ede3dfc0fbc9d9c5118583 – < b5ad887339503103d0fbe9827b16ad287597c275
    • affected 9e512eaaf8f4008c44ede3dfc0fbc9d9c5118583 – < a424a34b8faddf97b5af41689087e7a230f79ba7
    • affected bbec5998d7bd349730f59c959a8b00cfff816e34
    • affected 59f751db7f392fa7a58cbd972205982f7f4f5854
    • affected 5.10.235 – < 5.10.253
    • affected 5.15.179 – < 5.15.203
    • affected 6.1.129 – < 6.1.167
    • affected 6.6.79 – < 6.6.130
    • affected 6.12.16 – < 6.12.78
    • affected 5.4.291 – < 5.5
    • affected 6.13.4 – < 6.14
  • Linux · Linux

    • affected 6.14
    • unaffected < 6.14
    • unaffected 5.10.253 – ≤ 5.10.*
    • unaffected 5.15.203 – ≤ 5.15.*
    • unaffected 6.1.167 – ≤ 6.1.*
    • unaffected 6.6.130 – ≤ 6.6.*
    • unaffected 6.12.78 – ≤ 6.12.*
    • unaffected 6.18.20 – ≤ 6.18.*
    • unaffected 6.19.10 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-43061 badge
[![CVE-2026-43061](https://cveledger.app/badge/CVE-2026-43061.svg)](https://cveledger.app/cve/CVE-2026-43061)

Record last updated .