CVE Intelligence
Medium

CVE-2026-43061 — serial: 8250: Fix TX deadlock when using DMA

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.

Published May 5, 2026 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: Linux

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.1% (30-day exploitation probability)+0
  • Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.13%
ahead of 2% of scored CVEs · Oct 15, 2026
Affects
Linux
Linux and 1 more
CVSS base
5.5
Medium · 1 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Linux Linux, Linux Linux Kernel).
  2. Apply the fixed version or the patch documented under Remediation.
  3. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Linux Linux version 6.14≥ 7c47e637dfadfbc691dd297b91d81ef939ca2080 and < 8190f9ab6ad90cb97652adbebd238b874a4ef70d≥ bf3f395b9c37956eca866c9e1679769ed7dcce68 and < 79a19bd936bb35f56ef0ccab1b3b59ebce8c762d≥ d470522c597b73e63cca04f3012aec28185113b7 and < f76d91271bcacbd759a2e4ee3ea61faa6a727ccf≥ 5e00346deb7bf40a4cf70e3716ac8e9a2409eb55 and < d2719a0a9c3439abf67843a5504b7afccd9ded93≥ c8a52c772c7c6de72257a435bcad03d3bb914a70 and < 2a72403b985aea6b4aac3171830492f9a387f9e1≥ 9e512eaaf8f4008c44ede3dfc0fbc9d9c5118583 and < 5f6b17562f03fc65c7d3474ef8f1959b19d1ca41≥ 9e512eaaf8f4008c44ede3dfc0fbc9d9c5118583 and < b5ad887339503103d0fbe9827b16ad287597c275
and 10 more ≥ 9e512eaaf8f4008c44ede3dfc0fbc9d9c5118583 and < a424a34b8faddf97b5af41689087e7a230f79ba7version bbec5998d7bd349730f59c959a8b00cfff816e34version 59f751db7f392fa7a58cbd972205982f7f4f5854≥ 5.10.235 and < 5.10.253≥ 5.15.179 and < 5.15.203≥ 6.1.129 and < 6.1.167≥ 6.6.79 and < 6.6.130≥ 6.12.16 and < 6.12.78≥ 5.4.291 and < 5.5≥ 6.13.4 and < 6.14
Vulnerable CVE Program (cve.org) e CISA ADP
Linux Linux Kernel version 7.0-rc6version 7.0-rc7version 6.14-rc3≥ 5.10.235 and < 5.10.253≥ 5.15.179 and < 5.15.203≥ 6.1.129 and < 6.1.167≥ 6.6.79 and < 6.6.130≥ 6.12.16 and < 6.12.78
and 14 more ≥ 6.13.4 and < 6.14≥ 6.14.1 and < 6.18.20≥ 6.19 and < 6.19.10version 6.14≥ 5.4.291 and < 5.5version 6.14-rc4version 6.14-rc5version 6.14-rc6version 6.14-rc7version 7.0-rc1version 7.0-rc2version 7.0-rc3version 7.0-rc4version 7.0-rc5
Vulnerable NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
5.5 CVSS 3.1 Medium 1.8 3.6 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H (score shown at the top: nvd@nist.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-667

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 15, 2026 · 3 reading(s) · max 0.13%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
endpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · linux/linux
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • Fix documented
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVSS changed · 5.5
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Analyzed
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVE published
    May 5, 2026 · Linux

Source activity

Repeated readings are counted rather than listed.

  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

8 on the record

Elsewhere on this site

Linux
every CVE for this vendor
CWE-667
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-99999 ipv4: validate checksum_start before completing checksum 1d
  • CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 1d
  • CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 2d
  • CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 2d
  • CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 2d
  • CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 2d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No CISA SSVC assessment.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-43061 is "serial: 8250: Fix TX deadlock when using DMA", rated Medium. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.5 describes technical severity. EPSS 0.13% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.