CVE-2026-63821

wifi: rtw88: usb: fix memory leaks on USB write failures

N/A
Published: July 19, 2026 at 12:02 PM UTC
Updated: August 17, 2026 at 05:17 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: rtw88: usb: fix memory leaks on USB write failures When rtw_usb_write_port() fails to submit a USB Request Block (URB) (e.g., due to device disconnect or ENOMEM), the completion callback is never executed. Currently, the driver ignores the return value of rtw_usb_write_port() in rtw_usb_write_data() and rtw_usb_tx_agg_skb(). Because these functions rely on the completion callback to free the socket buffers (skbs) and the transaction control block (txcb), a submission failure results in: 1. A memory leak of the allocated skb in rtw_usb_write_data(). 2. A memory leak of the txcb structure and all aggregated skbs in rtw_usb_tx_agg_skb(). Fix this by checking the return value of rtw_usb_write_port(). If it fails, explicitly free the skb in rtw_usb_write_data(), and properly purge the tx_ack_queue and free the txcb in rtw_usb_tx_agg_skb(). The issue was discovered in practice during device disconnect/reconnect scenarios and memory pressure conditions. Tested by verifying normal TX operation continues after the fix without regressions.

Affected

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

6.2 ≤ v < 6.12.956.2 ≤ v < 6.18.386.2 ≤ v < 6.6.1446.2 ≤ v < 7.1.36.2 ≤ v < 7.26.2a82dfd33d1237f6c0fb8a7077022189d1fc7ec98
Vendor states this is fixed in 200d58c851b8f63f77a05570072dd20f79bc3681 (fixed)
Vendor states this is fixed in 2b2060c2075a72bc2de43ce5e1b9347d6c5e27bb (fixed)
Vendor states this is fixed in 53fed4061a09755de99c89fdc7fae5b794da455f (fixed)
Vendor states this is fixed in 6b964941bbfe6e0f18b1a5e008486dbb62df440a (fixed)
Vendor states this is fixed in 8206d173d18ef5a077423119f4e9a93cb3a6f4eb (fixed)
Vendor states this is fixed in 6.12.95 (unaffected)
Vendor states this is fixed in 6.18.38 (unaffected)
Vendor states this is fixed in 6.2 (unaffected)
Vendor states this is fixed in 6.6.144 (unaffected)
Vendor states this is fixed in 7.1.3 (unaffected)
Vendor states this is fixed in 7.2 (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

StatusAWAITING ANALYSIS

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