LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53529: wifi: rtw88: Fix memory leak in rtw88_usb

In the Linux kernel, the following vulnerability has been resolved: wifi: rtw88: Fix memory leak in rtw88_usb Kmemleak shows the following leak arising from routine in the usb probe routine: unreferenced object 0xffff895cb29bba00 (size 512): comm "(udev-worker)", pid 534, jiffies 4294903932 (age 102751.088s) hex dump (first 32 bytes): 77 30 30 30 00 00 00 00 02 2f 2d 2b 30 00 00 00 w000...../-+0... 02 00 2a 28 00 00 00 00 ff 55 ff ff ff 00 00 00 ..*(.....U...... backtrace: [<ffffffff9265fa36>] kmalloc_trace+0x26/0x90 [<ffffffffc17eec41>] rtw_usb_probe+0x2f1/0x680 [rtw_usb] [<ffffffffc03e19fd>] usb_probe_interface+0xdd/0x2e0 [usbcore] [<ffffffff92b4f2fe>] really_probe+0x18e/0x3d0 [<ffffffff92b4f5b8>] __driver_probe_device+0x78/0x160 [<ffffffff92b4f6bf>] driver_probe_device+0x1f/0x90 [<ffffffff92b4f8df>] __driver_attach+0xbf/0x1b0 [<ffffffff92b4d350>] bus_for_each_dev+0x70/0xc0 [<ffffffff92b4e51e>] bus_add_driver+0x10e/0x210 [<ffffffff92b50935>] driver_register+0x55/0xf0 [<ffffffffc03e0708>] usb_register_driver+0x88/0x140 [usbcore] [<ffffffff92401153>] do_one_initcall+0x43/0x210 [<ffffffff9254f42a>] do_init_module+0x4a/0x200 [<ffffffff92551d1c>] __do_sys_finit_module+0xac/0x120 [<ffffffff92ee6626>] do_syscall_64+0x56/0x80 [<ffffffff9300006a>] entry_SYSCALL_64_after_hwframe+0x46/0xb0 The leak was verified to be real by unloading the driver, which resulted in a dangling pointer to the allocation. The allocated memory is freed in rtw_usb_intf_deinit().

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

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel memory leak in the Realtek rtw88 USB Wi-Fi driver. When affected systems probe a supported USB Wi-Fi interface, allocated memory may not be released correctly. The source describes a leak and dangling pointer after driver unload, not remote code execution or confirmed compromise.

Executive priority

Treat as routine kernel maintenance unless affected USB Wi-Fi deployments are widespread or resource exhaustion risk is operationally important. No source evidence indicates emergency exploitation pressure.

Technical view

CVE-2023-53529 is fixed in Linux stable commits for rtw88_usb. Kmemleak traced an unreferenced 512-byte allocation to rtw_usb_probe(). The report says unloading the driver confirmed a dangling pointer, and the allocated memory is now freed in rtw_usb_intf_deinit().

Likely exposure

Exposure is most likely on Linux systems using affected kernels with the rtw88 USB Wi-Fi driver and compatible Realtek USB Wi-Fi hardware. Systems without that driver loaded or without relevant USB Wi-Fi devices are less likely to be exposed.

Exploitation context

The provided sources do not report active exploitation, public exploit code, KEV listing, privilege escalation, or remote attack behavior. Evidence supports a local kernel driver resource-management flaw triggered during USB driver probing.

Researcher notes

The source bundle lacks CVSS, CWE, and detailed version-range semantics. Analysis should stay tied to rtw88_usb probe/deinit behavior and the two Linux stable commits. Validate exact affectedness against the running distribution kernel source or advisory.

Mitigation direction

  • Update to a Linux kernel containing the referenced stable fixes.
  • Check distribution vendor advisories for backported kernel packages.
  • Avoid loading rtw88_usb on systems that do not need it.
  • Confirm Realtek USB Wi-Fi support is still required on affected assets.

Validation and detection

  • Inventory Linux kernel versions and vendor backport status.
  • Check whether the rtw88_usb module is present or loaded.
  • Identify hosts using Realtek USB Wi-Fi adapters.
  • Review kernel logs or kmemleak findings for rtw_usb_probe leaks.
Prepared
Confidence
medium
Sources
4

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-53529 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
3Source 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
LinuxLinuxe3037485c68ec1a299ff41160d8fedbd4abc29b9, e3037485c68ec1a299ff41160d8fedbd4abc29b9unaffected
LinuxLinux5.2, 0, 6.3.4, 6.4affected
Weakness

CWE details

No CWE listed

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