# CVE-2026-80769: HID: rapoo: fix missing hid_is_usb() check

> A missing check in the Linux kernel HID rapoo driver allows local attackers to trigger a kernel crash via uhid devices.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-80769, GHSA-cqwg-p2fx-632h, UBUNTU-CVE-2026-80769

## What is CVE-2026-80769?

CVE-2026-80769 is a vulnerability in Linux, published on 4 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

HID: rapoo: fix missing hid_is_usb() check

to_usb_interface() can only be used on a hid_device whose parent is really
USB; uhid can create devices that identify as being on BUS_USB, but don't
actually have a USB parent.
Fix the use of to_usb_interface() without a hid_is_usb() check.

Add a dependency on USB_HID for hid_is_usb(), as other HID drivers do; the
alternative would be to provide a simple stub implementation on !USB_HID
builds.

I have verified that it is currently possible to trigger a kernel splat due
to this bug in an ASAN build, and that this commit fixes the issue.

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


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

Apply the vendor's patch.

## Is CVE-2026-80769 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-80769 is a vulnerability in Linux, published on 4 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-80769 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-80769/ (Markdown: https://insights.sbomify.com/CVE-2026-80769/index.md)
```

## Sources

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

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