CVE-2025-71100: wifi: rtlwifi: 8192cu: fix tid out of range in rtl92cu_tx_fill_desc()
In the Linux kernel, the following vulnerability has been resolved:
wifi: rtlwifi: 8192cu: fix tid out of range in rtl92cu_tx_fill_desc()
TID getting from ieee80211_get_tid() might be out of range of array size
of sta_entry->tids[], so check TID is less than MAX_TID_COUNT. Othwerwise,
UBSAN warn:
UBSAN: array-index-out-of-bounds in drivers/net/wireless/realtek/rtlwifi/rtl8192cu/trx.c:514:30
index 10 is out of range for type 'rtl_tid_data [9]'
Security readout for executives and security teams
Plain-English summary
A flaw in Linux’s Realtek RTL8192CU Wi-Fi driver can access memory outside an expected array when processing an invalid traffic identifier. Systems using this driver may face crashes or other memory-safety effects. The supplied CVSS score is 7.6, driven primarily by potential availability impact.
Executive priority
Treat as a high-priority patching issue for systems actively using RTL8192CU Wi-Fi, especially availability-sensitive endpoints. It is not evidence of an internet-wide emergency: exposure appears hardware- and driver-specific, requires adjacent access, and active exploitation is not documented in the supplied sources.
Technical view
rtl92cu_tx_fill_desc() uses a TID returned by ieee80211_get_tid() to index sta_entry->tids[]. A value such as 10 exceeds the nine-element array. The kernel fix checks that TID is below MAX_TID_COUNT. UBSAN confirmed the out-of-bounds access; the sources do not establish code execution.
Likely exposure
Exposure is limited to Linux systems using the rtlwifi RTL8192CU wireless driver on affected kernels. The CVSS vector indicates an adjacent-network attack surface without privileges or user interaction. The supplied version data is ambiguous, so kernel version alone is insufficient for confirming exposure.
Exploitation context
The bundle provides no evidence of active exploitation, and the CVE is not listed as KEV. The stated attack vector is adjacent, suggesting an attacker must be within a relevant local wireless or network context. No public exploit capability is established by these sources.
Researcher notes
The demonstrated condition is an array-index-out-of-bounds read or write context in transmit descriptor handling, with index 10 against rtl_tid_data[9]. The sources show a bounds-check remediation but do not describe controlled corruption, privilege escalation, or code execution. Version-range interpretation should be verified against distribution advisories and referenced stable commits.
Mitigation direction
Install a vendor-supported kernel containing the referenced TID bounds-check fix.
Check distribution security guidance to identify the corrected package for each deployed kernel.
Disable or replace affected RTL8192CU hardware where prompt kernel updates are impractical.
Prioritize exposed wireless endpoints and systems where availability is operationally important.
Validation and detection
Inventory systems using the rtlwifi RTL8192CU driver and associated Realtek USB wireless hardware.
Record running kernel and distribution package versions on identified systems.
Confirm the installed kernel contains the referenced fix through vendor advisories or source provenance.
After updating, verify the corrected kernel is running and the affected driver remains operational.
Monitor kernel logs for UBSAN array-index warnings or unexplained wireless-related crashes.
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-2025-71100 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
1CVSS vectors
3Timeline events
0ADP providers
4Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.