# CVE-2023-54110: usb: rndis_host: Secure rndis_query check against int overflow

> An integer overflow in the Linux kernel RNDIS host driver allows attackers to leak sensitive information via crafted USB responses.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Dec 2025
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2023-54110, DEBIAN-CVE-2023-54110, GHSA-cffh-ppgh-4vqx, UBUNTU-CVE-2023-54110

## What is CVE-2023-54110?

CVE-2023-54110 is a vulnerability in Linux, published on 24 Dec 2025. 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:

usb: rndis_host: Secure rndis_query check against int overflow

Variables off and len typed as uint32 in rndis_query function
are controlled by incoming RNDIS response message thus their
value may be manipulated. Setting off to a unexpectetly large
value will cause the sum with len and 8 to overflow and pass
the implemented validation step. Consequently the response
pointer will be referring to a location past the expected
buffer boundaries allowing information leakage e.g. via
RNDIS_OID_802_3_PERMANENT_ADDRESS OID.

## Which versions are affected by CVE-2023-54110?


## How do I fix CVE-2023-54110?

Apply the vendor's patch.

## Is CVE-2023-54110 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-54110 and fix it if it is affected.

What it is: CVE-2023-54110 is a vulnerability in Linux, published on 24 Dec 2025. 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-2023-54110 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-2023-54110/ (Markdown: https://insights.sbomify.com/CVE-2023-54110/index.md)
```

## Sources

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

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