# CVE-2021-46906: HID: usbhid: fix info leak in hid_submit_ctrl

> A local attacker can trigger an information leak of up to 16384 bytes in the Linux kernel USB HID driver by submitting a zero-size report.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **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:** 26 Feb 2024
- **Updated:** 11 May 2026
- **Also known as:** DEBIAN-CVE-2021-46906, GHSA-jc66-9qcw-88hp, UBUNTU-CVE-2021-46906

## What is CVE-2021-46906?

CVE-2021-46906 is a medium-severity vulnerability in Linux kernel, published on 26 Feb 2024. 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: usbhid: fix info leak in hid_submit_ctrl

In hid_submit_ctrl(), the way of calculating the report length doesn't
take into account that report->size can be zero. When running the
syzkaller reproducer, a report of size 0 causes hid_submit_ctrl) to
calculate transfer_buffer_length as 16384. When this urb is passed to
the usb core layer, KMSAN reports an info leak of 16384 bytes.

To fix this, first modify hid_report_len() to account for the zero
report size case by using DIV_ROUND_UP for the division. Then, call it
from hid_submit_ctrl().

Weakness: CWE-668 (Exposure of Resource to Wrong Sphere)

## Which versions are affected by CVE-2021-46906?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2021-46906?

Apply the vendor's patch.

## Is CVE-2021-46906 being exploited?

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

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-46906 and fix it if it is affected.

What it is: CVE-2021-46906 is a medium-severity vulnerability in Linux kernel, published on 26 Feb 2024. 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-2021-46906 in the wild and no public exploit code.

Affected product: Linux kernel. 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-2021-46906/ (Markdown: https://insights.sbomify.com/CVE-2021-46906/index.md)
```

## Sources

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

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