Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-80770: HID: nintendo: stop device IO before hid_hw_stop on probe failure

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.21% (FIRST EPSS).
  • Fixed version: Linux Linux 03a84f9f88b42cd49752ec0259922b67e4b88598, 13a3edf96568a0b7aacadea07c2adec53ac8f630, 1f74d3bff6fe04a64e02ab3661d2e0d554565aa6.

Low priority for now. Upgrade to Linux Linux 03a84f9f88b42cd49752ec0259922b67e4b88598, 13a3edf96568a0b7aacadea07c2adec53ac8f630, 1f74d3bff6fe04a64e02ab3661d2e0d554565aa6 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: HID: nintendo: stop device IO before hid_hw_stop on probe failure nintendo_hid_probe() calls hid_device_io_start() before joycon_init() and joycon_leds_create(). If either fails, the error path jumps to err_close which calls hid_hw_close()/hid_hw_stop() without first calling hid_device_io_stop(). hid_hw_stop() does not stop device IO, so hid_input_report() may still run and access driver data that is being torn down, resulting in a use-after-free. Add an err_io_stop label that calls hid_device_io_stop() before hid_hw_close(), and point the two post-io_start error paths at it.

—No exploit Fix available
Published
Sep 4, 2026
Updated
Oct 19, 2026
EPSS
0.2% · 11th 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-80770

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

    • 5.16affected
    • 2af16c1f846bd60240745bbd3afa13d5f040c61a and later · before c2f3d51c7f5222f5b51e0c90f02258d82e1b44ddaffected · git
    • 2af16c1f846bd60240745bbd3afa13d5f040c61a and later · before c023443f0e6cfd257846b6515c93c1ea08026593affected · git
    • 2af16c1f846bd60240745bbd3afa13d5f040c61a and later · before 03a84f9f88b42cd49752ec0259922b67e4b88598affected · git
    • 2af16c1f846bd60240745bbd3afa13d5f040c61a and later · before 5efcd7bbfaaec67d137c99aa0940fa34375db27faffected · git
    • 2af16c1f846bd60240745bbd3afa13d5f040c61a and later · before 13a3edf96568a0b7aacadea07c2adec53ac8f630affected · git
    • 2af16c1f846bd60240745bbd3afa13d5f040c61a and later · before 2e0d98dc8a6dea5fc2b72bf66e0dcbd5488644b4affected · git
    • 2af16c1f846bd60240745bbd3afa13d5f040c61a and later · before 1f74d3bff6fe04a64e02ab3661d2e0d554565aa6affected · git
    • before 5.16not affected · semver
    • 6.1.187 and later · up to and including 6.1.*not 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.187-16.1.187-1
Debian:12linux-6.12before 6.12.107-1~deb12u16.12.107-1~deb12u1
Debian:13linuxbefore 6.12.107-16.12.107-1
Debian:14linuxbefore 7.1.12-17.1.12-1
openSUSE:Tumbleweedkernel-sourcebefore 7.2.5-1.17.2.5-1.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-80768Sep 4, 2026 · HID: ft260: fix stack-use-after-return write in I2C read race
    0Monitor
  • ← EarlierCVE-2026-80769Sep 4, 2026 · HID: rapoo: fix missing hid_is_usb() check
    0Monitor
  • Later →CVE-2026-80771Sep 4, 2026 · HID: nintendo: register input device after capabilities are set
    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 Linux03a84f9f88b42cd49752ec0259922b67e4b88598Vendor (CNA)
Linux Linux13a3edf96568a0b7aacadea07c2adec53ac8f630Vendor (CNA)
Linux Linux1f74d3bff6fe04a64e02ab3661d2e0d554565aa6Vendor (CNA)
Linux Linux2e0d98dc8a6dea5fc2b72bf66e0dcbd5488644b4Vendor (CNA)
Linux Linux5efcd7bbfaaec67d137c99aa0940fa34375db27fVendor (CNA)
Linux Linuxc023443f0e6cfd257846b6515c93c1ea08026593Vendor (CNA)
Linux Linuxc2f3d51c7f5222f5b51e0c90f02258d82e1b44ddVendor (CNA)
azl3 kernel 6.6.150.1-1 on Azure Linux 3.0—Microsoft (MSRC)
debian:linux6.1.187-1 · Debian:12Package registry (OSV)
debian:linux-6.126.12.107-1~deb12u1 · Debian:12Package registry (OSV)
opensuse:kernel-source7.2.5-1.1 · openSUSE:TumbleweedPackage 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 (6 more)

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

All records