CVE-2026-80737: serial: amba-pl011: synchronize DMA teardown
Noroxi assessment
Priority: Monitor (action score 31/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.12% (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 440915499231e9db1c361aa45bb702e8fd3b4a32, 44bd0ecc3444882d08ecfbc2b2418d2f463d3186, 5974cb66681eac367107b05924744d7e3b49d41c; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1.
Low priority for now. Upgrade to Linux Linux 440915499231e9db1c361aa45bb702e8fd3b4a32, 44bd0ecc3444882d08ecfbc2b2418d2f463d3186, 5974cb66681eac367107b05924744d7e3b49d41c; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1 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: 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.
- Published
- Sep 3, 2026
- Updated
- Oct 16, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- —
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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.
—
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
- 2.6.39affected
- ead76f329f777c7301e0a5456a0a1c7a081570bd and later · before a38fae9d212e2d3ed5e9ec0ef773f8c0a27fb76eaffected · git
- ead76f329f777c7301e0a5456a0a1c7a081570bd and later · before 44bd0ecc3444882d08ecfbc2b2418d2f463d3186affected · git
- ead76f329f777c7301e0a5456a0a1c7a081570bd and later · before f70c9d4fba46463a5b1c7b3ee9ee3b40c90dac03affected · git
- ead76f329f777c7301e0a5456a0a1c7a081570bd and later · before c8c8e895f65fbf71ea6224e27cf8dab91b776e0daffected · git
- ead76f329f777c7301e0a5456a0a1c7a081570bd and later · before 9f6989e477f03a4721d34bb4b09b17accd40283eaffected · git
- ead76f329f777c7301e0a5456a0a1c7a081570bd and later · before 5974cb66681eac367107b05924744d7e3b49d41caffected · git
- ead76f329f777c7301e0a5456a0a1c7a081570bd and later · before fdfb46c387241b4eddd36d746793764413285913affected · git
- ead76f329f777c7301e0a5456a0a1c7a081570bd and later · before 440915499231e9db1c361aa45bb702e8fd3b4a32affected · git
- before 2.6.39not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.107-1~deb12u1 | 6.12.107-1~deb12u1 |
| Debian:13 | linux | before 6.12.107-1 | 6.12.107-1 |
| Debian:14 | linux | before 7.1.9-1 | 7.1.9-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-80731Sep 3, 2026 · net: remove CAP_SYS_RAWIO zero-padding in dev_validate_header31Monitor
- ← EarlierCVE-2026-80734Sep 3, 2026 · btrfs: initialize inode mapping flags for cached inodes35Monitor
- Later →CVE-2026-80738Sep 3, 2026 · bpf: Check sk_state before sk_protocol in bpf_tcp_*_syncookie29Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 440915499231e9db1c361aa45bb702e8fd3b4a32 | Vendor (CNA) |
| Linux Linux | 44bd0ecc3444882d08ecfbc2b2418d2f463d3186 | Vendor (CNA) |
| Linux Linux | 5974cb66681eac367107b05924744d7e3b49d41c | Vendor (CNA) |
| Linux Linux | 9f6989e477f03a4721d34bb4b09b17accd40283e | Vendor (CNA) |
| Linux Linux | a38fae9d212e2d3ed5e9ec0ef773f8c0a27fb76e | Vendor (CNA) |
| Linux Linux | c8c8e895f65fbf71ea6224e27cf8dab91b776e0d | Vendor (CNA) |
| Linux Linux | f70c9d4fba46463a5b1c7b3ee9ee3b40c90dac03 | Vendor (CNA) |
| Linux Linux | fdfb46c387241b4eddd36d746793764413285913 | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | 6.6.157.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.107-1~deb12u1 · Debian:12 | Package 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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
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
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/44bd0ecc3444882d08ecfbc2b2418d2f463d3186
- git.kernel.org/stable/c/5974cb66681eac367107b05924744d7e3b49d41c
- git.kernel.org/stable/c/9f6989e477f03a4721d34bb4b09b17accd40283e
- git.kernel.org/stable/c/a38fae9d212e2d3ed5e9ec0ef773f8c0a27fb76e
- git.kernel.org/stable/c/c8c8e895f65fbf71ea6224e27cf8dab91b776e0d
- git.kernel.org/stable/c/f70c9d4fba46463a5b1c7b3ee9ee3b40c90dac03
- git.kernel.org/stable/c/fdfb46c387241b4eddd36d746793764413285913
Vendor advisories and official records. Exploit/PoC links are deliberately left out.