Input: ati_remote2 - fix type confusion in device attribute handlers
- 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.113, 6.18.57, 7.2.11
- 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: Input: ati_remote2 - fix type confusion in device attribute handlers Previously, the channel_mask and mode_mask attributes were registered on the parent usb_device via sysfs_create_group(). When commit b20d6bf8014b ("Input: ati-remote2 - use driver core to instantiate device attributes") converted the driver to let the driver core manage them via dev_groups in struct usb_driver, the attributes moved to the bound usb_interface devices, but the show and store callbacks were not updated accordingly. As a result, the callbacks still invoked to_usb_device() on a device pointer belonging to a struct usb_interface, producing an invalid usb_device pointer. Use to_usb_interface() directly in the attribute handlers to obtain the interface and its driver data.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Linux Linux
From b20d6bf8014b2d6fcf65c150453d95a6276fd1fa · fixed in e44ec6b6d3c0b8ea089b589fa0cce49a4da66b89; From b20d6bf8014b2d6fcf65c150453d95a6276fd1fa · fixed in d738e51bf2c21921df351f536147178ae3cbd38b; From b20d6bf8014b2d6fcf65c150453d95a6276fd1fa · fixed in 2caae9d1977beea0a7914b3d86639262801fd116; From b20d6bf8014b2d6fcf65c150453d95a6276fd1fa · fixed in f321cc430c49b6c1be0d53f2ef19d8342d8029cc
- Linux Linux
6.11
- KernelLinux
From 6.11.0 · fixed in 6.12.113; From 6.13.0 · fixed in 6.18.57; From 6.19.0 · fixed in 7.2.11