CVE-2026-80770

What the bug is

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.

Where it lives

The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.

drivers/hid/hid-nintendo.c

What this is

NINTENDO HID DRIVERMAINTAINERS section matched on drivers/hid/hid-nintendo* · linux-input@vger.kernel.org · Maintained

Kernel module

hid_nintendo

Check it on the machine

grep -wE 'CONFIG_HID|CONFIG_HID_NINTENDO|CONFIG_HID_SUPPORT' /boot/config-$(uname -r)

Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.

lsmod | grep -w hid_nintendo

Prints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.

Show whether Debian builds this, per release

Debian builds this, but not on every flavour. At least one release below builds the code on some of its kernel flavours and not on others, so the answer depends on the architecture and flavour installed.

• bookworm, trixieMnot built on arm64/cloud-arm64
• forky, sidMnot built on amd64/cloud-amd64, arm64/cloud-arm64
• bookworm · linux-6.12Mnot built on arm64/cloud-arm64

M

a module where it is built at all; some flavours do not build it

Build switches

CONFIG_HID, CONFIG_HID_NINTENDO, CONFIG_HID_SUPPORT

Reads as

all on means the file is compiled; any one off means it is not.

From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages

Signals

Published

2026-09-04 (44 days ago)source

CVSS

no vector published, unrated

Attack vector

not published

EPSS

0.21%, higher than 11.1% of all CVEssource

CISA KEV

not listedthe KEV catalogue

Debian urgency

not yet assignedsource

Subsystem

drivers/hid

Upstream fixes

The versions the CNA records as introducing and fixing this, and the commit for each. source

Introduced	Fixed in	Commit
5.16	6.1.187	c2f3d51c7f52
5.16	6.6.156	c023443f0e6c
5.16	6.12.106	03a84f9f88b4
5.16	6.18.47	5efcd7bbfaae
5.16	7.1.11	13a3edf96568
5.16	7.2.1	2e0d98dc8a6d
5.16	7.3	1f74d3bff6fe

Debian advisories