LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23073: wifi: rsi: Fix memory corruption due to not set vif driver data size

In the Linux kernel, the following vulnerability has been resolved: wifi: rsi: Fix memory corruption due to not set vif driver data size The struct ieee80211_vif contains trailing space for vif driver data, when struct ieee80211_vif is allocated, the total memory size that is allocated is sizeof(struct ieee80211_vif) + size of vif driver data. The size of vif driver data is set by each WiFi driver as needed. The RSI911x driver does not set vif driver data size, no trailing space for vif driver data is therefore allocated past struct ieee80211_vif . The RSI911x driver does however use the vif driver data to store its vif driver data structure "struct vif_priv". An access to vif->drv_priv leads to access out of struct ieee80211_vif bounds and corruption of some memory. In case of the failure observed locally, rsi_mac80211_add_interface() would write struct vif_priv *vif_info = (struct vif_priv *)vif->drv_priv; vif_info->vap_id = vap_idx. This write corrupts struct fq_tin member struct list_head new_flows . The flow = list_first_entry(head, struct fq_flow, flowchain); in fq_tin_reset() then reports non-NULL bogus address, which when accessed causes a crash. The trigger is very simple, boot the machine with init=/bin/sh , mount devtmpfs, sysfs, procfs, and then do "ip link set wlan0 up", "sleep 1", "ip link set wlan0 down" and the crash occurs. Fix this by setting the correct size of vif driver data, which is the size of "struct vif_priv", so that memory is allocated and the driver can store its driver data in it, instead of corrupting memory around it.

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

Security readout for executives and security teams

Plain-English summary

CVE-2026-23073 is a Linux kernel bug in the RSI911x WiFi driver. The driver writes private WiFi interface data without reserving memory for it, corrupting nearby kernel memory and causing crashes. Business risk is mainly availability for systems using this specific WiFi driver.

Executive priority

Treat as a targeted patching item, not an internet-wide emergency. Prioritize systems where WiFi availability matters or RSI911x hardware is deployed. The urgency increases for embedded or unattended devices that may crash and require manual recovery.

Technical view

The RSI911x mac80211 driver fails to set the ieee80211_vif driver-data size, but still writes a struct vif_priv through vif->drv_priv. That out-of-bounds write can corrupt adjacent kernel structures, with the source describing a crash path involving fq_tin_reset(). Stable kernel fixes set the correct driver-data size.

Likely exposure

Exposure appears limited to Linux systems using affected kernel versions with the RSI911x WiFi driver and relevant hardware enabled. Systems without that driver or hardware are less likely to be exposed. The CVE record lists affected Linux kernel lines but does not provide CPEs or distribution package names.

Exploitation context

The CVE source describes a simple local crash trigger during WiFi interface up/down handling, but it does not claim active exploitation. CISA KEV status is false in the supplied bundle. No public exploit status beyond the kernel report is provided.

Researcher notes

The source evidence supports kernel memory corruption and denial-of-service behavior, but not privilege escalation, remote reachability, or active exploitation. The affected-version data is sparse and distribution mapping is absent, so validation should focus on driver presence and fixed commit backports.

Mitigation direction

  • Apply Linux stable or distribution kernel updates containing the referenced RSI911x fixes.
  • Check vendor or distribution advisories for exact fixed package versions.
  • Prioritize endpoints, appliances, or embedded systems with RSI911x WiFi hardware enabled.
  • Do not rely on undocumented workarounds; follow vendor guidance if patching is delayed.

Validation and detection

  • Inventory Linux systems for affected kernel branches and RSI911x driver usage.
  • Confirm the running kernel includes one of the referenced stable fix commits or a vendor backport.
  • Review kernel logs for RSI911x-related crashes or memory corruption symptoms.
  • Test normal WiFi interface lifecycle in a controlled environment after patching.
Prepared
Confidence
medium
Sources
9

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-2026-23073 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
8Source 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
LinuxLinuxdad0d04fa7ba41ce603a01e8e64967650303e9a2, dad0d04fa7ba41ce603a01e8e64967650303e9a2, dad0d04fa7ba41ce603a01e8e64967650303e9a2, dad0d04fa7ba41ce603a01e8e64967650303e9a2, dad0d04fa7ba41ce603a01e8e64967650303e9a2, dad0d04fa7ba41ce603a01e8e64967650303e9a2, dad0d04fa7ba41ce603a01e8e64967650303e9a2unaffected
LinuxLinux3.15, 0, 5.10.249, 5.15.199, 6.1.162, 6.6.122, 6.12.68, 6.18.8, 6.19affected
Weakness

CWE details

No CWE listed

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