CVE-2026-99069: Linux kernel · Input: ati_remote2 – fix type confusion in device attribute handlers
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in f321cc430c49b6c1be0d53f2ef19d8342d8029cc : update Linux kernel when convenient.
Data as of 26 Oct 2026, 13:07 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in f321cc430c49b6c1be0d53f2ef19d8342d8029cc, e44ec6b6d3c0b8ea089b589fa0cce49a4da66b89, d738e51bf2c21921df351f536147178ae3cbd38b +1
Exploitation evidence
Disclosed: evidence found.
CVE published 23 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade Linux kernel to f321cc430c49b6c1be0d53f2ef19d8342d8029cc, e44ec6b6d3c0b8ea089b589fa0cce49a4da66b89, d738e51bf2c21921df351f536147178ae3cbd38b or 2caae9d1977beea0a7914b3d86639262801fd116.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
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.
References
- git.kernel.org/stable/c/e44ec6b6d3c0b8ea089b589fa0cce49a4da66b89 (opens in a new tab)
- git.kernel.org/stable/c/d738e51bf2c21921df351f536147178ae3cbd38b (opens in a new tab)
- git.kernel.org/stable/c/2caae9d1977beea0a7914b3d86639262801fd116 (opens in a new tab)
- git.kernel.org/stable/c/f321cc430c49b6c1be0d53f2ef19d8342d8029cc (opens in a new tab)