cveboard RSS feed

CVE-2026-23073

CVE.org · Published

Historical CVEsJSONAI instructions

Record status
Published
Identifier year (not publication year)
2026
Source publication
Source updated
Imported by cveboard
Source snapshot
cve_2026-10-24_midnight_baseline ·

Plain text

CNA source text (English)

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.

Scoped product and version facts

Fix information unknown; no fixed version is derived here. Missing information does not prove that no fix exists.

Exploitation unknown; this catalogue does not assess exploitation.

Linux

Vendor
Linux
Product
Linux
Platforms
Unknown
Default status
unaffected
Linux · Scoped product and version facts
Version (version)Status (status)Version scheme (versionType)Exclusive end (lessThan)Inclusive end (lessThanOrEqual)Status changes (at → status)
dad0d04fa7ba41ce603a01e8e64967650303e9a2affectedgit49ef094fdbc3526e5db2aebb404b84f79c5603dcUnavailableNone listed
dad0d04fa7ba41ce603a01e8e64967650303e9a2affectedgit0d7c9e793e351cbbe9e06a9ca47d77b6ad288fb0UnavailableNone listed
dad0d04fa7ba41ce603a01e8e64967650303e9a2affectedgit7c54d0c3e2cad4300be721ec2aecfcf8a63bc9f4UnavailableNone listed
dad0d04fa7ba41ce603a01e8e64967650303e9a2affectedgit7761d7801f40e61069b4df3db88b36d80d089f8aUnavailableNone listed
dad0d04fa7ba41ce603a01e8e64967650303e9a2affectedgit99129d80a5d4989ef8566f434f3589f60f28042bUnavailableNone listed
dad0d04fa7ba41ce603a01e8e64967650303e9a2affectedgit31efbcff90884ea5f65bf3d1de01267db51ee3d1UnavailableNone listed
dad0d04fa7ba41ce603a01e8e64967650303e9a2affectedgit4f431d88ea8093afc7ba55edf4652978c5a68f33UnavailableNone listed

Linux

Vendor
Linux
Product
Linux
Platforms
Unknown
Default status
affected
Linux · Scoped product and version facts
Version (version)Status (status)Version scheme (versionType)Exclusive end (lessThan)Inclusive end (lessThanOrEqual)Status changes (at → status)
3.15affectedUnavailableUnavailableUnavailableNone listed
0unaffectedsemver3.15UnavailableNone listed
5.10.249unaffectedsemverUnavailable5.10.*None listed
5.15.199unaffectedsemverUnavailable5.15.*None listed
6.1.162unaffectedsemverUnavailable6.1.*None listed
6.6.122unaffectedsemverUnavailable6.6.*None listed
6.12.68unaffectedsemverUnavailable6.12.*None listed
6.18.8unaffectedsemverUnavailable6.18.*None listed
6.19unaffectedoriginal_commit_for_fixUnavailable*None listed