# CVE-2022-50733: usb: idmouse: fix an uninit-value in idmouse_open

> A local attacker with physical access can trigger an uninitialized memory read in the idmouse USB driver, potentially disclosing kernel memory contents.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 24 Dec 2025
- **Updated:** 11 May 2026
- **Also known as:** DEBIAN-CVE-2022-50733, GHSA-3qmv-4mq3-fcr8, UBUNTU-CVE-2022-50733

## What is CVE-2022-50733?

CVE-2022-50733 is a vulnerability in Linux, published on 24 Dec 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

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

usb: idmouse: fix an uninit-value in idmouse_open

In idmouse_create_image, if any ftip_command fails, it will
go to the reset label. However, this leads to the data in
bulk_in_buffer[HEADER..IMGSIZE] uninitialized. And the check
for valid image incurs an uninitialized dereference.

Fix this by moving the check before reset label since this
check only be valid if the data after bulk_in_buffer[HEADER]
has concrete data.

Note that this is found by KMSAN, so only kernel compilation
is tested.

## Which versions are affected by CVE-2022-50733?


## How do I fix CVE-2022-50733?

Apply the vendor's patch.

## Is CVE-2022-50733 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-50733 and fix it if it is affected.

What it is: CVE-2022-50733 is a vulnerability in Linux, published on 24 Dec 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-50733 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-2022-50733/ (Markdown: https://insights.sbomify.com/CVE-2022-50733/index.md)
```

## Sources

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

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