CVE-2026-23073

wifi: rsi: Fix memory corruption due to not set vif driver data size

State
Published
Severity
Not scored
Published
Feb 4, 2026
Updated
Oct 19, 2026
Reserved
Jan 13, 2026

Read the record on cve.org

Description

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.

Scores

The record has no CVSS score.

Weaknesses

Affected Products

ProductVersions
LinuxLinux
  • dad0d04fa7ba41ce603a01e8e64967650303e9a2 to before 49ef094fdbc3526e5db2aebb404b84f79c5603dcAffected
  • dad0d04fa7ba41ce603a01e8e64967650303e9a2 to before 0d7c9e793e351cbbe9e06a9ca47d77b6ad288fb0Affected
  • dad0d04fa7ba41ce603a01e8e64967650303e9a2 to before 7c54d0c3e2cad4300be721ec2aecfcf8a63bc9f4Affected
  • dad0d04fa7ba41ce603a01e8e64967650303e9a2 to before 7761d7801f40e61069b4df3db88b36d80d089f8aAffected
  • dad0d04fa7ba41ce603a01e8e64967650303e9a2 to before 99129d80a5d4989ef8566f434f3589f60f28042bAffected
  • dad0d04fa7ba41ce603a01e8e64967650303e9a2 to before 31efbcff90884ea5f65bf3d1de01267db51ee3d1Affected
  • dad0d04fa7ba41ce603a01e8e64967650303e9a2 to before 4f431d88ea8093afc7ba55edf4652978c5a68f33Affected
LinuxLinux
  • 3.15Affected
  • before 3.15Not affected
  • 5.10.249 through 5.10.*Not affected
  • 5.15.199 through 5.15.*Not affected
  • 6.1.162 through 6.1.*Not affected
  • 6.6.122 through 6.6.*Not affected
  • 6.12.68 through 6.12.*Not affected
  • 6.18.8 through 6.18.*Not affected
  • 6.19 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.