# wifi: rtw88: Fix memory leak in rtw88_usb

CVE record · `CVE-2023-53529`

- **Identifiers:** `CVE-2023-53529`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 1 Oct 2025
- **Updated:** 5 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 1 Oct 2025, 11:46 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `e3037485c68ec1a299ff41160d8fedbd4abc29b9 to before 5bba1ad561a8b5bb14704d8f511cf10466336e3d` (git)
  - affected: `e3037485c68ec1a299ff41160d8fedbd4abc29b9 to before 59a3a312009723e3e5082899655fdcc420e2b47a` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `5.2`
  - unaffected: `before 5.2` (semver)
  - unaffected: `6.3.4 to 6.3.*, inclusive` (semver)
  - unaffected: `6.4 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The rtw88_usb Wi-Fi driver in the Linux kernel, affected from 5.2 until fixed, leaks memory during USB probe. The source gives few details on what an attacker would need, and it describes only the leak and a dangling pointer left after the driver is unloaded. Upgrade to Linux 6.3.4 or later in the 6.3 series, or to 6.4 or later.

Written 16 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0013, the 2nd percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 1 Oct 2025, 11:46 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2023-53529)
- 1 Oct 2025, 12:15 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2023-53529)

## Sources

- [CVE List: CVE-2023-53529](https://www.cve.org/CVERecord?id=CVE-2023-53529)
- [NVD: CVE-2023-53529](https://nvd.nist.gov/vuln/detail/CVE-2023-53529)

### References from the CNA

- <https://git.kernel.org/stable/c/5bba1ad561a8b5bb14704d8f511cf10466336e3d>
- <https://git.kernel.org/stable/c/59a3a312009723e3e5082899655fdcc420e2b47a>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2023-53529>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2023-53529/>. Everything for agents: <https://agentprime.io/llms.txt>.
