# CVE-2023-54036: wifi: rtl8xxxu: Fix memory leaks with RTL8723BU, RTL8192EU

> A memory leak in the Linux kernel rtl8xxxu WiFi driver allows attackers to cause denial of service via Bluetooth traffic or rate changes.

- **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-54036, DEBIAN-CVE-2023-54036, GHSA-j3w7-7qhh-rrr2, UBUNTU-CVE-2023-54036

## What is CVE-2023-54036?

CVE-2023-54036 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:

wifi: rtl8xxxu: Fix memory leaks with RTL8723BU, RTL8192EU

The wifi + bluetooth combo chip RTL8723BU can leak memory (especially?)
when it's connected to a bluetooth audio device. The busy bluetooth
traffic generates lots of C2H (card to host) messages, which are not
freed correctly.

To fix this, move the dev_kfree_skb() call in rtl8xxxu_c2hcmd_callback()
inside the loop where skb_dequeue() is called.

The RTL8192EU leaks memory because the C2H messages are added to the
queue and left there forever. (This was fine in the past because it
probably wasn't sending any C2H messages until commit e542e66b7c2e
("wifi: rtl8xxxu: gen2: Turn on the rate control"). Since that commit
it sends a C2H message when the TX rate changes.)

To fix this, delete the check for rf_paths > 1 and the goto. Let the
function process the C2H messages from RTL8192EU like the ones from
the other chips.

Theoretically the RTL8188FU could also leak like RTL8723BU, but it
most likely doesn't send C2H messages frequently enough.

This change was tested with RTL8723BU by Erhard F. I tested it with
RTL8188FU and RTL8192EU.

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


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

Apply the vendor's patch.

## Is CVE-2023-54036 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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