Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

MediumCVSS 5.5 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.09% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 2a72403b985aea6b4aac3171830492f9a387f9e1, 5.10.253, 5.15.203.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 2a72403b985aea6b4aac3171830492f9a387f9e1, 5.10.253, 5.15.203 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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
Nov 11, 2026
EPSS
0.0% · 0th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.0%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-43061

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • bbec5998d7bd349730f59c959a8b00cfff816e34, 59f751db7f392fa7a58cbd972205982f7f4f5854, 6.14affected
    • 7c47e637dfadfbc691dd297b91d81ef939ca2080 and later · before 8190f9ab6ad90cb97652adbebd238b874a4ef70daffected · git
    • bf3f395b9c37956eca866c9e1679769ed7dcce68 and later · before 79a19bd936bb35f56ef0ccab1b3b59ebce8c762daffected · git
    • d470522c597b73e63cca04f3012aec28185113b7 and later · before f76d91271bcacbd759a2e4ee3ea61faa6a727ccfaffected · git
    • 5e00346deb7bf40a4cf70e3716ac8e9a2409eb55 and later · before d2719a0a9c3439abf67843a5504b7afccd9ded93affected · git
    • c8a52c772c7c6de72257a435bcad03d3bb914a70 and later · before 2a72403b985aea6b4aac3171830492f9a387f9e1affected · git
    • 9e512eaaf8f4008c44ede3dfc0fbc9d9c5118583 and later · before 5f6b17562f03fc65c7d3474ef8f1959b19d1ca41affected · git
    • 9e512eaaf8f4008c44ede3dfc0fbc9d9c5118583 and later · before b5ad887339503103d0fbe9827b16ad287597c275affected · git
    • 9e512eaaf8f4008c44ede3dfc0fbc9d9c5118583 and later · before a424a34b8faddf97b5af41689087e7a230f79ba7affected · git
    • 5.10.235 and later · before 5.10.253affected · semver
Affected versions · NVD (11)

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel5.4.291 and later · before 5.5
  • linux linux kernel5.10.235 and later · before 5.10.253
  • linux linux kernel5.15.179 and later · before 5.15.203
  • linux linux kernel6.1.129 and later · before 6.1.167
  • linux linux kernel6.6.79 and later · before 6.6.130
  • linux linux kernel6.12.16 and later · before 6.12.78
  • linux linux kernel6.13.4 and later · before 6.14
  • linux linux kernel6.14.1 and later · before 6.18.20
  • linux linux kernel6.19 and later · before 6.19.10
  • linux linux kernel6.14
  • linux linux kernel7.0

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.170-16.1.170-1
Debian:13linuxbefore 6.12.85-16.12.85-1
Debian:14linuxbefore 6.19.10-16.19.10-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-43059May 5, 2026 · Bluetooth: MGMT: Fix list corruption and UAF in command complete handlers
    31Monitor
  • ← EarlierCVE-2026-43060May 5, 2026 · netfilter: nft_ct: drop pending enqueued packets on removal
    31Monitor
  • Later →CVE-2026-43062May 5, 2026 · Bluetooth: L2CAP: Fix type confusion in l2cap_ecred_reconf_rsp()
    28Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux2a72403b985aea6b4aac3171830492f9a387f9e1Vendor (CNA)
Linux Linux5.10.253Vendor (CNA)
Linux Linux5.15.203Vendor (CNA)
Linux Linux5.5Vendor (CNA)
Linux Linux5f6b17562f03fc65c7d3474ef8f1959b19d1ca41Vendor (CNA)
Linux Linux6.1.167Vendor (CNA)
Linux Linux6.12.78Vendor (CNA)
Linux Linux6.14Vendor (CNA)
Linux Linux6.6.130Vendor (CNA)
Linux Linux79a19bd936bb35f56ef0ccab1b3b59ebce8c762dVendor (CNA)
Linux Linux8190f9ab6ad90cb97652adbebd238b874a4ef70dVendor (CNA)
Linux Linuxa424a34b8faddf97b5af41689087e7a230f79ba7Vendor (CNA)
Linux Linuxb5ad887339503103d0fbe9827b16ad287597c275Vendor (CNA)
Linux Linuxd2719a0a9c3439abf67843a5504b7afccd9ded93Vendor (CNA)
Linux Linuxf76d91271bcacbd759a2e4ee3ea61faa6a727ccfVendor (CNA)
debian:linux6.1.170-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-667 · Improper Locking

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records