HID: nintendo: register input device after capabilities are set
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.12.106, 6.18.47, 7.1.11, 7.2.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 2af16c1f846bd60240745bbd3afa13d5f040c61a · fixed in 3288bec1a21d582b504344380139cdc0e88ebe4d; From 2af16c1f846bd60240745bbd3afa13d5f040c61a · fixed in 268679f501386ad46405d42c2bcf89384cb5e256; From 2af16c1f846bd60240745bbd3afa13d5f040c61a · fixed in a9fc7547f911ada09da33c5e204e5acda38e765a; From 2af16c1f846bd60240745bbd3afa13d5f040c61a · fixed in 27dc4b8eadac73b3c3cc526c8547d8b4ae8528be; From 2af16c1f846bd60240745bbd3afa13d5f040c61a · fixed in d723bc1fe2e72b9252234e94c11af644ec477bf7
- Linux Linux
5.16
- KernelLinux
From 5.16.0 · fixed in 6.12.106; From 6.13.0 · fixed in 6.18.47; From 6.19.0 · fixed in 7.1.11; From 7.2.0 · fixed in 7.2.1