Answer in brief
CVE-2026-99069 records a Unknown severity vulnerability in Input: ati_remote2 - fix type confusion in device attribute handlers. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=b20d6bf8014b2d6fcf65c150453d95a6276fd1fa <e44ec6b6d3c0b8ea089b589fa0cce49a4da66b89 || >=b20d6bf8014b2d6fcf65c150453d95a6276fd1fa <d738e51bf2c21921df351f536147178ae3cbd38b || >=b20d6bf8014b2d6fcf65c150453d95a6276fd1fa <2caae9d1977beea0a7914b3d86639262801fd116 || >=b20d6bf8014b2d6fcf65c150453d95a6276fd1fa <f321cc430c49b6c1be0d53f2ef19d8342d8029cc | e44ec6b6d3c0b8ea089b589fa0cce49a4da66b89, d738e51bf2c21921df351f536147178ae3cbd38b, 2caae9d1977beea0a7914b3d86639262801fd116, f321cc430c49b6c1be0d53f2ef19d8342d8029cc |
| Linux/Linuxgeneric | 6.11 | Not reported |
Published upstream
Oct 23, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 23, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 23, 2026
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.
Quoted source text, attributed separately from HOL analysis.