CVE-2025-71234: wifi: rtl8xxxu: fix slab-out-of-bounds in rtl8xxxu_sta_add
In the Linux kernel, the following vulnerability has been resolved:
wifi: rtl8xxxu: fix slab-out-of-bounds in rtl8xxxu_sta_add
The driver does not set hw->sta_data_size, which causes mac80211 to
allocate insufficient space for driver private station data in
__sta_info_alloc(). When rtl8xxxu_sta_add() accesses members of
struct rtl8xxxu_sta_info through sta->drv_priv, this results in a
slab-out-of-bounds write.
KASAN report on RISC-V (VisionFive 2) with RTL8192EU adapter:
BUG: KASAN: slab-out-of-bounds in rtl8xxxu_sta_add+0x31c/0x346
Write of size 8 at addr ffffffd6d3e9ae88 by task kworker/u16:0/12
Set hw->sta_data_size to sizeof(struct rtl8xxxu_sta_info) during
probe, similar to how hw->vif_data_size is configured. This ensures
mac80211 allocates sufficient space for the driver's per-station
private data.
Tested on StarFive VisionFive 2 v1.2A board.
Security readout for executives and security teams
Plain-English summary
A Linux Wi-Fi driver bug can write past allocated kernel memory when adding a station for rtl8xxxu-supported Realtek USB adapters. The public record describes a KASAN-detected slab out-of-bounds write and a kernel fix. Business exposure appears limited to Linux systems using this driver and hardware path.
Executive priority
Treat as targeted infrastructure hygiene rather than broad emergency response. Prioritize patching laptops, embedded Linux, test rigs, and appliances that use Realtek USB Wi-Fi with rtl8xxxu, while awaiting fuller severity and exploitability details from vendors.
Technical view
rtl8xxxu did not set hw->sta_data_size, so mac80211 allocated too little private station data in __sta_info_alloc(). rtl8xxxu_sta_add() then accessed struct rtl8xxxu_sta_info through sta->drv_priv, causing a slab-out-of-bounds write. The fix sets hw->sta_data_size during probe.
Likely exposure
Likely exposed assets are Linux systems using the rtl8xxxu Wi-Fi driver, especially with Realtek USB adapters such as the RTL8192EU noted in testing. The source bundle lists affected Linux kernel versions, but does not provide a complete distribution-level mapping.
Exploitation context
The bundle does not report active exploitation, public exploit availability, KEV listing, or remote attack requirements. Evidence is limited to a KASAN report on a RISC-V VisionFive 2 board with an RTL8192EU adapter and upstream stable kernel fixes.
Researcher notes
The vulnerability is a kernel driver private-data allocation mismatch. Impact beyond memory corruption is not characterized in the provided sources. Avoid assuming privilege escalation, remote exploitation, or broad Wi-Fi exposure without additional vendor analysis or a scored advisory.
Mitigation direction
Identify Linux hosts using rtl8xxxu-supported Realtek USB Wi-Fi adapters.
Apply vendor or distribution kernel updates containing the referenced stable fixes.
If immediate patching is unavailable, reduce reliance on affected Wi-Fi adapters where practical.
Monitor Linux distribution advisories for backported fixed kernel packages.
Validation and detection
Check running kernel versions against distribution advisories for CVE-2025-71234.
Inventory loaded modules and hardware for rtl8xxxu and Realtek USB Wi-Fi usage.
Confirm patched kernels include the rtl8xxxu sta_data_size fix.
Review kernel logs for KASAN or memory corruption reports if debug builds are 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-2025-71234 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.
0CVSS vectors
3Timeline events
0ADP providers
5Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Feb 18, 2026, 14:53 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.