Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 22 days later

    Published

  3. · 9 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-23073, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.18% · top 92% of all CVEs (13 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected dad0d04fa7ba41ce603a01e8e64967650303e9a2 – < 49ef094fdbc3526e5db2aebb404b84f79c5603dc
    • affected dad0d04fa7ba41ce603a01e8e64967650303e9a2 – < 0d7c9e793e351cbbe9e06a9ca47d77b6ad288fb0
    • affected dad0d04fa7ba41ce603a01e8e64967650303e9a2 – < 7c54d0c3e2cad4300be721ec2aecfcf8a63bc9f4
    • affected dad0d04fa7ba41ce603a01e8e64967650303e9a2 – < 7761d7801f40e61069b4df3db88b36d80d089f8a
    • affected dad0d04fa7ba41ce603a01e8e64967650303e9a2 – < 99129d80a5d4989ef8566f434f3589f60f28042b
    • affected dad0d04fa7ba41ce603a01e8e64967650303e9a2 – < 31efbcff90884ea5f65bf3d1de01267db51ee3d1
    • affected dad0d04fa7ba41ce603a01e8e64967650303e9a2 – < 4f431d88ea8093afc7ba55edf4652978c5a68f33

  • Linux · Linux

    • affected 3.15
    • unaffected < 3.15
    • unaffected 5.10.249 – ≤ 5.10.*
    • unaffected 5.15.199 – ≤ 5.15.*
    • unaffected 6.1.162 – ≤ 6.1.*
    • unaffected 6.6.122 – ≤ 6.6.*
    • unaffected 6.12.68 – ≤ 6.12.*
    • unaffected 6.18.8 – ≤ 6.18.*
    • unaffected 6.19 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-23073 badge
[![CVE-2026-23073](https://cveledger.app/badge/CVE-2026-23073.svg)](https://cveledger.app/cve/CVE-2026-23073)

Record last updated .