# CVE-2023-54001: staging: r8712: Fix memory leak in _r8712_init_xmit_priv()

> A memory leak in the r8712 wireless driver can lead to resource exhaustion and denial of service.

- **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-54001, DEBIAN-CVE-2023-54001, GHSA-4vvr-5h54-mv77, UBUNTU-CVE-2023-54001

## What is CVE-2023-54001?

CVE-2023-54001 is a memory corruption 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:

staging: r8712: Fix memory leak in _r8712_init_xmit_priv()

In the above mentioned routine, memory is allocated in several places.
If the first succeeds and a later one fails, the routine will leak memory.
This patch fixes commit 2865d42c78a9 ("staging: r8712u: Add the new driver
to the mainline kernel"). A potential memory leak in
r8712_xmit_resource_alloc() is also addressed.

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


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

Apply the vendor's patch.

## Is CVE-2023-54001 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-54001 is a memory corruption 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-54001 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-54001/ (Markdown: https://insights.sbomify.com/CVE-2023-54001/index.md)
```

## Sources

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

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