# CVE-2026-80771: HID: nintendo: register input device after capabilities are set

> A race condition in the Linux kernel Nintendo HID driver allows local attackers to cause a denial of service via NULL pointer dereference.

- **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-99624, BELL-CVE-2026-80771, DEBIAN-CVE-2026-80771, GHSA-x6pf-56pg-q32p, UBUNTU-CVE-2026-80771

## What is CVE-2026-80771?

CVE-2026-80771 is a 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: register input device after capabilities are set

input_register_device() exposes the device to userspace immediately.
In joycon_input_create() it was called before joycon_config_rumble()
configures the FF_RUMBLE capability and the memless force-feedback
device, so a concurrent EVIOCSFF could dereference a NULL dev->ff.

Registering early also means the initial udev event lacks button and
axis information, which can make input managers ignore the device.

Move input_register_device() to the end of joycon_input_create(), after
all capabilities, the IMU input device and the force-feedback callbacks
have been configured.

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


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

Apply the vendor's patch.

## Is CVE-2026-80771 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-80771 is a 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-80771 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-80771/ (Markdown: https://insights.sbomify.com/CVE-2026-80771/index.md)
```

## Sources

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

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