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

> A use-after-free in the Linux kernel Nintendo HID driver allows local attackers to execute code or escalate privileges via a race condition during device probe failure.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-99591, BELL-CVE-2026-80770, DEBIAN-CVE-2026-80770, GHSA-ghrw-6c83-p2qc, UBUNTU-CVE-2026-80770

## What is CVE-2026-80770?

CVE-2026-80770 is an use after free vulnerability in Linux, published on 4 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:

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.

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


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

Apply the vendor's patch.

## Is CVE-2026-80770 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-80770 is an use after free vulnerability in Linux, published on 4 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-80770 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-80770/ (Markdown: https://insights.sbomify.com/CVE-2026-80770/index.md)
```

## Sources

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

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