CVE-2026-43061

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-05-05. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

May 5, 2026

Last Modified

May 29, 2026

Advisory Details (8)

Auto-updated Aug 2, 2026
No patch confirmed yet.
generic

serial: 8250: Fix TX deadlock when using DMA - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f76d91271bcacbd759a2e4ee3ea61faa6a727ccf
generic

serial: 8250: Fix TX deadlock when using DMA - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d2719a0a9c3439abf67843a5504b7afccd9ded93
generic

serial: 8250: Fix TX deadlock when using DMA - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b5ad887339503103d0fbe9827b16ad287597c275
generic

serial: 8250: Fix TX deadlock when using DMA - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a424a34b8faddf97b5af41689087e7a230f79ba7
generic

serial: 8250: Fix TX deadlock when using DMA - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8190f9ab6ad90cb97652adbebd238b874a4ef70d
generic

serial: 8250: Fix TX deadlock when using DMA - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/79a19bd936bb35f56ef0ccab1b3b59ebce8c762d
generic

serial: 8250: Fix TX deadlock when using DMA - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5f6b17562f03fc65c7d3474ef8f1959b19d1ca41
generic

serial: 8250: Fix TX deadlock when using DMA - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2a72403b985aea6b4aac3171830492f9a387f9e1

Vendor Advisories for CVE-2026-43061(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(27)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-6.8 (6.8.0-136.136) @ noble2026-08-23ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1064.72+fips1) @ noble2026-08-23ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1075 (5.15.0-1075.79) @ jammy2026-08-23ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.66~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1058.61) @ noble2026-08-23ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1059.62.1) @ noble2026-08-23ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1107.107) @ jammy2026-08-23ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.64) @ jammy2026-08-23ubuntu
ubuntulinux-tools-ibm-edge (5.15.0.1106.110~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1063.71~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-08-23ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1109.105) @ jammy2026-08-23ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1117.126) @ jammy2026-08-23ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-aws-edge (6.8.0-1061.64~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1033.34) @ noble2026-08-23ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-intel-iotg-edge (5.15.0.1107.113~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-tools-intel-iotg-5.15 (5.15.0.1107.106) @ jammy2026-08-23ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2050.52) @ noble2026-08-23ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1109.115~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1112.122~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1117.102) @ jammy2026-08-23ubuntu
linuxKernel @ 5.10.253—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (53 versions)5.10.257-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (122 versions)6.19.10-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(25)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 7× in last 7d / 28× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 157 total refreshes for this CVE.

  1. 2026-09-13 16:47 UTCEPSS rescore
  2. 2026-09-12 15:01 UTCEPSS rescore
  3. 2026-09-11 17:23 UTCOSV refresh
  4. 2026-09-11 14:53 UTCEPSS rescore
  5. 2026-09-11 09:37 UTCEPSS rescore
  6. 2026-09-10 09:34 UTCEPSS rescore
  7. 2026-09-08 22:00 UTCEPSS rescore
  8. 2026-09-07 16:01 UTCEPSS rescore
  9. 2026-09-06 13:47 UTCEPSS rescore
  10. 2026-09-04 05:06 UTCEPSS rescore
  11. 2026-09-02 14:12 UTCEPSS rescore
  12. 2026-09-01 13:54 UTCEPSS rescore
  13. 2026-08-28 21:41 UTCEPSS rescore
  14. 2026-08-27 14:25 UTCEPSS rescore
  15. 2026-08-26 14:46 UTCEPSS rescore
  16. 2026-08-25 13:49 UTCEPSS rescore
  17. 2026-08-23 21:00 UTCEG score recompute
  18. 2026-08-23 21:00 UTCVendor advisory
  19. 2026-08-23 21:00 UTCGHSA enrichment
  20. 2026-08-23 00:19 UTCEPSS rescore
  21. 2026-08-21 23:49 UTCEPSS rescore
  22. 2026-08-20 22:55 UTCEPSS rescore
  23. 2026-08-19 17:03 UTCEPSS rescore
  24. 2026-08-17 13:47 UTCEPSS rescore
  25. 2026-08-17 13:03 UTCEG score recompute
Show 75 more
  1. 2026-08-17 13:03 UTCVendor advisory
  2. 2026-08-17 13:03 UTCGHSA enrichment
  3. 2026-08-16 14:56 UTCEPSS rescore
  4. 2026-08-16 04:59 UTCEG score recompute
  5. 2026-08-16 04:59 UTCVendor advisory
  6. 2026-08-16 04:59 UTCGHSA enrichment
  7. 2026-08-16 02:14 UTCEPSS rescore
  8. 2026-08-15 01:30 UTCEPSS rescore
  9. 2026-08-14 03:35 UTCVendor advisory
  10. 2026-08-14 03:34 UTCGHSA enrichment
  11. 2026-08-12 17:12 UTCVendor advisory
  12. 2026-08-12 17:12 UTCGHSA enrichment
  13. 2026-08-11 08:09 UTCVendor advisory
  14. 2026-08-11 08:09 UTCGHSA enrichment
  15. 2026-08-10 06:35 UTCEG score recompute
  16. 2026-08-10 06:35 UTCVendor advisory
  17. 2026-08-10 06:35 UTCGHSA enrichment
  18. 2026-08-09 13:46 UTCEPSS rescore
  19. 2026-08-09 05:05 UTCEG score recompute
  20. 2026-08-09 05:05 UTCVendor advisory
  21. 2026-08-09 05:05 UTCGHSA enrichment
  22. 2026-08-08 16:37 UTCEPSS rescore
  23. 2026-08-08 03:35 UTCEG score recompute
  24. 2026-08-08 03:35 UTCVendor advisory
  25. 2026-08-08 03:35 UTCGHSA enrichment
  26. 2026-08-07 02:05 UTCVendor advisory
  27. 2026-08-07 02:05 UTCGHSA enrichment
  28. 2026-08-05 22:26 UTCEG score recompute
  29. 2026-08-05 22:26 UTCVendor advisory
  30. 2026-08-05 22:26 UTCGHSA enrichment
  31. 2026-08-05 19:17 UTCEPSS rescore
  32. 2026-08-04 15:10 UTCEPSS rescore
  33. 2026-08-03 19:57 UTCEG score recompute
  34. 2026-08-03 19:57 UTCVendor advisory
  35. 2026-08-03 19:57 UTCGHSA enrichment
  36. 2026-08-03 10:36 UTCEPSS rescore
  37. 2026-08-02 05:17 UTCEG score recompute
  38. 2026-08-02 05:17 UTCVendor advisory
  39. 2026-08-02 05:17 UTCGHSA enrichment
  40. 2026-08-02 02:27 UTCEPSS rescore
  41. 2026-08-01 04:16 UTCEPSS rescore
  42. 2026-07-30 16:28 UTCEPSS rescore
  43. 2026-07-27 14:13 UTCEPSS rescore
  44. 2026-07-26 14:54 UTCEPSS rescore
  45. 2026-07-26 14:54 UTCEPSS rescore
  46. 2026-07-25 14:18 UTCEPSS rescore
  47. 2026-07-24 14:17 UTCEPSS rescore
  48. 2026-07-23 14:18 UTCEPSS rescore
  49. 2026-07-23 03:13 UTCEG score recompute
  50. 2026-07-22 14:08 UTCEPSS rescore
  51. 2026-07-20 17:08 UTCEPSS rescore
  52. 2026-07-19 17:48 UTCOSV refresh
  53. 2026-07-19 02:29 UTCEPSS rescore
  54. 2026-07-18 10:04 UTCEPSS rescore
  55. 2026-07-16 17:03 UTCEPSS rescore
  56. 2026-07-15 16:57 UTCEPSS rescore
  57. 2026-07-15 02:00 UTCEPSS rescore
  58. 2026-07-13 22:30 UTCEPSS rescore
  59. 2026-07-12 05:46 UTCEPSS rescore
  60. 2026-07-11 08:27 UTCEPSS rescore
  61. 2026-07-09 19:10 UTCEPSS rescore
  62. 2026-07-08 15:16 UTCEPSS rescore
  63. 2026-07-07 13:46 UTCEPSS rescore
  64. 2026-07-06 16:27 UTCEPSS rescore
  65. 2026-07-04 06:31 UTCEPSS rescore
  66. 2026-07-01 15:06 UTCEPSS rescore
  67. 2026-06-30 23:22 UTCEPSS rescore
  68. 2026-06-29 14:06 UTCEPSS rescore
  69. 2026-06-28 14:07 UTCEPSS rescore
  70. 2026-06-28 04:56 UTCEPSS rescore
  71. 2026-06-25 13:49 UTCEPSS rescore
  72. 2026-06-25 13:49 UTCEPSS rescore
  73. 2026-06-24 14:05 UTCEPSS rescore
  74. 2026-06-23 21:33 UTCEPSS rescore
  75. 2026-06-21 01:59 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-43061?
CVE-2026-43061 is a medium vulnerability published on May 5, 2026. In the Linux kernel, the following vulnerability has been resolved: serial: 8250: Fix TX deadlock when using DMA dmaengineterminateasync does not guarantee that the dmatxcomplete callback will run. The callback is currently the only place where dma->tx_running gets cleared. If the transaction is…
When was CVE-2026-43061 disclosed?
CVE-2026-43061 was first published in the National Vulnerability Database on May 5, 2026, with the most recent update on May 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43061 actively exploited?
CVE-2026-43061 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 99.5% of all scored CVEs.
What is the CVSS score of CVE-2026-43061?
CVE-2026-43061 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-43061?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43061, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-43061

Explore →

Is Your Infrastructure Affected by CVE-2026-43061?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs