CVE-2026-80770: HID: nintendo: stop device IO before hid_hw_stop on probe failure
HID: nintendo: stop device IO before hidhwstop on probe failure
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ubuntu/linux-hwe-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42~24.04.1 - Upgrade
Upgrade
ubuntu/linux-riscv-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1~24.04.1 - Upgrade
Upgrade
ubuntu/linuxto a version that resolves this vulnerability.Fixed in 7.0.0-42.42 - Upgrade
Upgrade
ubuntu/linux-awsto a version that resolves this vulnerability.Fixed in 7.0.0-1016.17 - Upgrade
Upgrade
ubuntu/linux-gcpto a version that resolves this vulnerability.Fixed in 7.0.0-1016.18 - Upgrade
Upgrade
ubuntu/linux-ibmto a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oem-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oracleto a version that resolves this vulnerability.Fixed in 7.0.0-1015.16 - Upgrade
Upgrade
ubuntu/linux-riscvto a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1
Event History
Frequently Asked Questions
When can the use-after-free occur?
It can occur when nintendo_hid_probe() has started device I/O and then either joycon_init() or joycon_leds_create() fails. The affected error path tears down driver data while input reports may still be processed.
What condition must be present for an attacker or triggering event to reach the vulnerable path?
The failure must happen after hid_device_io_start() and during joycon_init() or joycon_leds_create(). The provided information does not identify a remote attack vector, required privileges, or specific device interaction needed to induce those failures.
What is the relevant mitigation if the fix cannot be applied immediately?
The described flaw is in the Nintendo HID driver probe failure path. The provided data does not specify a supported configuration workaround or mitigation other than applying the resolved change that stops device I/O before hardware teardown.