# CVE-2026-80737: serial: amba-pl011: synchronize DMA teardown

> A race condition in the Linux kernel's AMBA PL011 serial driver allows use-after-free, potentially leading to code execution or denial of service.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Sep 2026
- **Updated:** 16 Oct 2026
- **Also known as:** AZL-99044, BELL-CVE-2026-80737, DEBIAN-CVE-2026-80737, GHSA-j4vm-79j3-8jfc, UBUNTU-CVE-2026-80737

## What is CVE-2026-80737?

CVE-2026-80737 is a high-severity use after free vulnerability in Linux, published on 3 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

serial: amba-pl011: synchronize DMA teardown

dmaengine_terminate_all() does not wait for a running callback, so the TX
callback can still touch the TX buffer after it is freed. The RX poll
timer reads the RX buffers without the port lock.

Switch to dmaengine_terminate_sync() and delete the RX timer before
freeing the buffers.

## Which versions are affected by CVE-2026-80737?


## How do I fix CVE-2026-80737?

Apply the vendor's patch.

## Is CVE-2026-80737 being exploited?

There is no known exploitation of CVE-2026-80737 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-80737 and fix it if it is affected.

What it is: CVE-2026-80737 is a high-severity use after free vulnerability in Linux, published on 3 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-80737 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-80737/ (Markdown: https://insights.sbomify.com/CVE-2026-80737/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-80737
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-80737
- OSV: https://osv.dev/vulnerability/CVE-2026-80737

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-80737/
Summaries are generated and may contain mistakes; the official description above is the record.