LiveActive security incident?Get immediate response
CVE Record

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

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2023-54036 is a Linux kernel WiFi driver memory leak affecting rtl8xxxu handling for some Realtek USB WiFi chips. On affected systems, repeated device messages can consume memory over time, especially with RTL8723BU during Bluetooth audio activity. No active exploitation is reported in the provided sources.

Executive priority

Treat this as a targeted availability risk, not a broad emergency. Prioritize patching only where affected Realtek WiFi hardware is deployed, especially endpoints or embedded systems that rely on long uptime.

Technical view

The rtl8xxxu driver failed to free queued C2H message buffers correctly. RTL8723BU could leak SKBs during frequent C2H traffic, and RTL8192EU could leave C2H messages queued indefinitely after rate-control behavior changed. Kernel stable commits adjust C2H processing and freeing behavior.

Likely exposure

Exposure appears limited to Linux systems using the rtl8xxxu driver with RTL8723BU or RTL8192EU devices. RTL8188FU is mentioned as theoretically possible but unlikely. Exact exposure depends on kernel version, downstream backports, and whether these adapters are present and active.

Exploitation context

The provided sources describe a memory leak, not a proven remote exploit path. KEV status is false, and no cited source reports active exploitation. Practical risk is more consistent with local or adjacent availability degradation where affected WiFi hardware is in use.

Researcher notes

Evidence is strongest for RTL8723BU and RTL8192EU behavior in rtl8xxxu. The source notes RTL8188FU theoretical leakage but likely low message frequency. No CVSS, CWE, exploit report, or complete downstream fixed-version matrix is provided.

Mitigation direction

  • Check vendor or distribution kernel advisories for CVE-2023-54036 coverage.
  • Update to a kernel package containing the referenced stable fixes.
  • Prioritize devices using RTL8723BU or RTL8192EU adapters.
  • Monitor affected hosts for memory growth during WiFi and Bluetooth activity.
  • Consider replacing or disabling affected adapters where patching is delayed.

Validation and detection

  • Inventory Linux hosts for rtl8xxxu driver usage.
  • Identify attached Realtek RTL8723BU and RTL8192EU USB WiFi devices.
  • Compare running kernel packages against vendor-fixed releases or stable commits.
  • Review logs and telemetry for sustained memory growth under affected workloads.
  • Confirm patched kernels include the linked rtl8xxxu C2H fixes.
Prepared
Confidence
medium
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-54036 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
6Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxe542e66b7c2ee2adeefdbb7f259f2f60cadf2819, e542e66b7c2ee2adeefdbb7f259f2f60cadf2819, e542e66b7c2ee2adeefdbb7f259f2f60cadf2819, e542e66b7c2ee2adeefdbb7f259f2f60cadf2819, e542e66b7c2ee2adeefdbb7f259f2f60cadf2819unaffected
LinuxLinux5.5, 0, 5.10.173, 5.15.99, 6.1.16, 6.2.3, 6.3affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.