CVE-2023-54036

wifi: rtl8xxxu: Fix memory leaks with RTL8723BU, RTL8192EU

N/A
Published: December 24, 2025 at 10:56 AM UTC
Updated: June 17, 2026 at 06:46 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.5 ≤ v < 5.10.1735.5 ≤ v < 5.15.995.5 ≤ v < 6.1.165.5 ≤ v < 6.2.35.5 ≤ v < 6.35.5e542e66b7c2ee2adeefdbb7f259f2f60cadf2819
Vendor states this is fixed in 35fb0e275af1aa1ca0a9784417e90f988aaf8e78 (fixed)
Vendor states this is fixed in 430f9f9bec53a75f9ccc53e156a66f13fc098b83 (fixed)
Vendor states this is fixed in 93c3f34ec02fc81188d328287d4fddd498ccddea (fixed)
Vendor states this is fixed in b39f662ce1648db0b9de32e6a849b098480793cb (fixed)
Vendor states this is fixed in f39a86b4efd270947ee252cc32a30b0aef492d65 (fixed)
Vendor states this is fixed in 5.10.173 (unaffected)
Vendor states this is fixed in 5.15.99 (unaffected)
Vendor states this is fixed in 5.5 (unaffected)
Vendor states this is fixed in 6.1.16 (unaffected)
Vendor states this is fixed in 6.2.3 (unaffected)
Vendor states this is fixed in 6.3 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card