Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-80886: serial: msm: Disable DMA for kernel console UART

Noroxi assessment

Priority: Monitor (action score 0/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.22% (FIRST EPSS).
  • Fixed version: Linux Linux 22dd2777e6c180e1c945b00f6d18550979436324, 2727744ccb5ca59090451451ee94f530b1be04a5, 6acea62738ed4cae6746483026706a773b44dad7.

Low priority for now. Upgrade to Linux Linux 22dd2777e6c180e1c945b00f6d18550979436324, 2727744ccb5ca59090451451ee94f530b1be04a5, 6acea62738ed4cae6746483026706a773b44dad7 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: msm: Disable DMA for kernel console UART At the moment, concurrent writes from userspace and the kernel to the console can trigger a race condition that results in an infinite loop of the same messages printed over and over again. This is most likely to happen during system startup or shutdown when the init system starts/stops a large number of system services that interact with various kernel code. When userspace writes to the TTY device, the driver initiates an asynchronous DMA transfer and releases the port lock. At the same moment, the kernel printk path might grab the port lock and re-configure the UART controller for PIO, without waiting for the DMA operation to complete. It seems like this collision results in zero progress being reported for the DMA engine, so the same text is printed to the console over and over again. For the kernel console, we want a reliable output path that will be functional even during crashes etc. So rather than implementing complex code to synchronize the kernel console write routines with the userspace DMA write routines, simply disable DMA for the console UART instance. Similar checks exist in many other serial drivers, e.g. 8250_port.c, imx.c, sh-sci.c etc.

—No exploit Fix available
Published
Sep 4, 2026
Updated
Sep 4, 2026
EPSS
0.2% · 12th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

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-80886

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 instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • 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 (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

Running WordPress? Scan your site free with WP Lens

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.

—

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

    • 4.4affected
    • 3a878c430fd6eb4f8587f9ebd187f773bf85d1d6 and later · before f58e568dc308c8e13f7730c8de2da5ed514e540daffected · git
    • 3a878c430fd6eb4f8587f9ebd187f773bf85d1d6 and later · before bb4296de5b538b575978c588cb3738ab8524d01aaffected · git
    • 3a878c430fd6eb4f8587f9ebd187f773bf85d1d6 and later · before 6acea62738ed4cae6746483026706a773b44dad7affected · git
    • 3a878c430fd6eb4f8587f9ebd187f773bf85d1d6 and later · before abc1926c88c189e5d698b91ed6890e09ab5c321daffected · git
    • 3a878c430fd6eb4f8587f9ebd187f773bf85d1d6 and later · before 2727744ccb5ca59090451451ee94f530b1be04a5affected · git
    • 3a878c430fd6eb4f8587f9ebd187f773bf85d1d6 and later · before d354716245192de2d203f2b35f22ab8dc13595e2affected · git
    • 3a878c430fd6eb4f8587f9ebd187f773bf85d1d6 and later · before e3b42e326f4f30efcdc90bad5f5ba37e1cd91a47affected · git
    • 3a878c430fd6eb4f8587f9ebd187f773bf85d1d6 and later · before 22dd2777e6c180e1c945b00f6d18550979436324affected · git
    • before 4.4not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.180-16.1.180-1
Debian:13linuxbefore 6.12.100-16.12.100-1
Debian:14linuxbefore 7.1.5-17.1.5-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-80882Sep 4, 2026 · crypto: tegra - Return ENOMEM when input buffer allocation fails for ccm
    0Monitor
  • ← EarlierCVE-2026-80885Sep 4, 2026 · afs: Fix uncancelled rxrpc OOB message handler
    0Monitor
  • Later →CVE-2026-80889Sep 4, 2026 · can: isotp: fix timer drain order, wakeup handling and tx_gen ordering
    0Monitor

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 Linux22dd2777e6c180e1c945b00f6d18550979436324Vendor (CNA)
Linux Linux2727744ccb5ca59090451451ee94f530b1be04a5Vendor (CNA)
Linux Linux6acea62738ed4cae6746483026706a773b44dad7Vendor (CNA)
Linux Linuxabc1926c88c189e5d698b91ed6890e09ab5c321dVendor (CNA)
Linux Linuxbb4296de5b538b575978c588cb3738ab8524d01aVendor (CNA)
Linux Linuxd354716245192de2d203f2b35f22ab8dc13595e2Vendor (CNA)
Linux Linuxe3b42e326f4f30efcdc90bad5f5ba37e1cd91a47Vendor (CNA)
Linux Linuxf58e568dc308c8e13f7730c8de2da5ed514e540dVendor (CNA)
debian:linux6.1.180-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.

EPSS, last 120 days

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 researchers

Finders, 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

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

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

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

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

All records