CVE-2026-99069: Linux kernel · Input: ati_remote2 – fix type confusion in device attribute handlers
Affects Linux kernelSource GCVE Database
Not known to be exploited.
Data as of 28 Oct 2026, 01:42 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.10linuxpkg:deb/ubuntu/linux?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Ubuntu 26.10linux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Ubuntu 26.10linux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Ubuntu 26.10linux-azure-fdepkg:deb/ubuntu/linux-azure-fde?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Ubuntu 26.10linux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Ubuntu 26.10linux-oraclepkg:deb/ubuntu/linux-oracle?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix for this vulnerability has been implemented in the Linux kernel. Users should apply the updated kernel versions that include the corrected attribute handlers using to_usb_interface().
Description
A type confusion vulnerability was fixed in the Linux kernel's ati_remote2 input driver. The issue involved device attribute handlers incorrectly using to_usb_device() on a usb_interface pointer, leading to invalid pointer usage. This was due to a change in how device attributes were managed, moving from the parent usb_device to the bound usb_interface devices without updating the callbacks accordingly.
References
- ubuntu.com/security/CVE-2026-99069 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-99069 (opens in a new tab)
- git.kernel.org/stable/c/2caae9d1977beea0a7914b3d86639262801fd116 (opens in a new tab)
- git.kernel.org/stable/c/d738e51bf2c21921df351f536147178ae3cbd38b (opens in a new tab)
- git.kernel.org/stable/c/e44ec6b6d3c0b8ea089b589fa0cce49a4da66b89 (opens in a new tab)
- git.kernel.org/stable/c/f321cc430c49b6c1be0d53f2ef19d8342d8029cc (opens in a new tab)