# serial: 8250: Fix TX deadlock when using DMA

CVE record · `CVE-2026-43061`

- **Identifiers:** `CVE-2026-43061`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 5 May 2026
- **Updated:** 6 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 5 May 2026, 15:17 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `7c47e637dfadfbc691dd297b91d81ef939ca2080 to before 8190f9ab6ad90cb97652adbebd238b874a4ef70d` (git)
  - affected: `bf3f395b9c37956eca866c9e1679769ed7dcce68 to before 79a19bd936bb35f56ef0ccab1b3b59ebce8c762d` (git)
  - affected: `d470522c597b73e63cca04f3012aec28185113b7 to before f76d91271bcacbd759a2e4ee3ea61faa6a727ccf` (git)
  - affected: `5e00346deb7bf40a4cf70e3716ac8e9a2409eb55 to before d2719a0a9c3439abf67843a5504b7afccd9ded93` (git)
  - affected: `c8a52c772c7c6de72257a435bcad03d3bb914a70 to before 2a72403b985aea6b4aac3171830492f9a387f9e1` (git)
  - affected: `9e512eaaf8f4008c44ede3dfc0fbc9d9c5118583 to before 5f6b17562f03fc65c7d3474ef8f1959b19d1ca41` (git)
  - affected: `9e512eaaf8f4008c44ede3dfc0fbc9d9c5118583 to before b5ad887339503103d0fbe9827b16ad287597c275` (git)
  - affected: `9e512eaaf8f4008c44ede3dfc0fbc9d9c5118583 to before a424a34b8faddf97b5af41689087e7a230f79ba7` (git)
  - affected: `bbec5998d7bd349730f59c959a8b00cfff816e34` (git)
  - affected: `59f751db7f392fa7a58cbd972205982f7f4f5854` (git)
  - affected: `5.10.235 to before 5.10.253` (semver)
  - affected: `5.15.179 to before 5.15.203` (semver)
  - and 5 more
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.14`
  - unaffected: `before 6.14` (semver)
  - unaffected: `5.10.253 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.203 to 5.15.*, inclusive` (semver)
  - unaffected: `6.1.167 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6.130 to 6.6.*, inclusive` (semver)
  - unaffected: `6.12.78 to 6.12.*, inclusive` (semver)
  - unaffected: `6.18.20 to 6.18.*, inclusive` (semver)
  - unaffected: `6.19.10 to 6.19.*, inclusive` (semver)
  - unaffected: `7.0 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0009, the 1st percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 5 May 2026, 15:17 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-43061)
- 5 May 2026, 16:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-43061)

## Sources

- [CVE List: CVE-2026-43061](https://www.cve.org/CVERecord?id=CVE-2026-43061)
- [NVD: CVE-2026-43061](https://nvd.nist.gov/vuln/detail/CVE-2026-43061)

### References from the CNA

- <https://git.kernel.org/stable/c/8190f9ab6ad90cb97652adbebd238b874a4ef70d>
- <https://git.kernel.org/stable/c/79a19bd936bb35f56ef0ccab1b3b59ebce8c762d>
- <https://git.kernel.org/stable/c/f76d91271bcacbd759a2e4ee3ea61faa6a727ccf>
- <https://git.kernel.org/stable/c/d2719a0a9c3439abf67843a5504b7afccd9ded93>
- <https://git.kernel.org/stable/c/2a72403b985aea6b4aac3171830492f9a387f9e1>
- <https://git.kernel.org/stable/c/5f6b17562f03fc65c7d3474ef8f1959b19d1ca41>
- <https://git.kernel.org/stable/c/b5ad887339503103d0fbe9827b16ad287597c275>
- <https://git.kernel.org/stable/c/a424a34b8faddf97b5af41689087e7a230f79ba7>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2026-43061>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2026-43061/>. Everything for agents: <https://agentprime.io/llms.txt>.
