Skip to main content
VulnerabilityPublished Updated

CVE-2026-23073: Linux kernel · Out-of-bounds Write

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in 99129d80a5d4989ef8566f434f3589f60f28042b : update Linux kernel when convenient.

Data as of 26 Oct 2026, 14:18 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS
0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Total control over the software or total information disclosure

CISA SSVC assessment, 2026-06-10.

Patch
Available – fixed in 99129d80a5d4989ef8566f434f3589f60f28042b, 7761d7801f40e61069b4df3db88b36d80d089f8a, 49ef094fdbc3526e5db2aebb404b84f79c5603dc +4

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ dad0d04fa7ba41ce603a01e8e64967650303e9a2, < 99129d80a5d4989ef8566f434f3589f60f28042b
Fixed in
  • 99129d80a5d4989ef8566f434f3589f60f28042b
LinuxLinuxAffected
  • ≥ dad0d04fa7ba41ce603a01e8e64967650303e9a2, < 7761d7801f40e61069b4df3db88b36d80d089f8a
Fixed in
  • 7761d7801f40e61069b4df3db88b36d80d089f8a
LinuxLinuxAffected
  • ≥ dad0d04fa7ba41ce603a01e8e64967650303e9a2, < 49ef094fdbc3526e5db2aebb404b84f79c5603dc
Fixed in
  • 49ef094fdbc3526e5db2aebb404b84f79c5603dc
LinuxLinuxAffected
  • ≥ dad0d04fa7ba41ce603a01e8e64967650303e9a2, < 31efbcff90884ea5f65bf3d1de01267db51ee3d1
Fixed in
  • 31efbcff90884ea5f65bf3d1de01267db51ee3d1
LinuxLinuxAffected
  • ≥ dad0d04fa7ba41ce603a01e8e64967650303e9a2, < 7c54d0c3e2cad4300be721ec2aecfcf8a63bc9f4
Fixed in
  • 7c54d0c3e2cad4300be721ec2aecfcf8a63bc9f4
LinuxLinuxAffected
  • ≥ dad0d04fa7ba41ce603a01e8e64967650303e9a2, < 4f431d88ea8093afc7ba55edf4652978c5a68f33
Fixed in
  • 4f431d88ea8093afc7ba55edf4652978c5a68f33

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.

References

Community reviews

Loading reviews…