# CVE-2026-99069: Input: ati_remote2 - fix type confusion in device attribute handlers


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 23 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** BELL-CVE-2026-99069, DEBIAN-CVE-2026-99069, GHSA-5wgj-7vcp-vw5x, UBUNTU-CVE-2026-99069

## What is CVE-2026-99069?

CVE-2026-99069 is a vulnerability in Linux, published on 23 Oct 2026. 

### Official 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.

## Which versions are affected by CVE-2026-99069?


## How do I fix CVE-2026-99069?

Upgrade to a fixed version.

## Is CVE-2026-99069 being exploited?

There is no known exploitation of CVE-2026-99069 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-99069 and fix it if it is affected.

What it is: CVE-2026-99069 is a vulnerability in Linux, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-99069 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-99069/ (Markdown: https://insights.sbomify.com/CVE-2026-99069/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-99069
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-99069
- OSV: https://osv.dev/vulnerability/CVE-2026-99069

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-99069/
Summaries are generated and may contain mistakes; the official description above is the record.