CVE-2026-23073: wifi: rsi: Fix memory corruption due to not set vif driver data size
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.18% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0d7c9e793e351cbbe9e06a9ca47d77b6ad288fb0, 31efbcff90884ea5f65bf3d1de01267db51ee3d1, 49ef094fdbc3526e5db2aebb404b84f79c5603dc.
Low priority for now. Upgrade to Linux Linux 0d7c9e793e351cbbe9e06a9ca47d77b6ad288fb0, 31efbcff90884ea5f65bf3d1de01267db51ee3d1, 49ef094fdbc3526e5db2aebb404b84f79c5603dc or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Feb 4, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 8th percentile
- CWE
- CWE-787
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel3.15 and later · before 5.10.249
- linux linux kernel5.11 and later · before 5.15.199
- linux linux kernel5.16 and later · before 6.1.162
- linux linux kernel6.2 and later · before 6.6.122
- linux linux kernel6.7 and later · before 6.12.68
- linux linux kernel6.13 and later · before 6.18.8
- linux linux kernel6.19
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 3.15affected
- dad0d04fa7ba41ce603a01e8e64967650303e9a2 and later · before 49ef094fdbc3526e5db2aebb404b84f79c5603dcaffected · git
- dad0d04fa7ba41ce603a01e8e64967650303e9a2 and later · before 0d7c9e793e351cbbe9e06a9ca47d77b6ad288fb0affected · git
- dad0d04fa7ba41ce603a01e8e64967650303e9a2 and later · before 7c54d0c3e2cad4300be721ec2aecfcf8a63bc9f4affected · git
- dad0d04fa7ba41ce603a01e8e64967650303e9a2 and later · before 7761d7801f40e61069b4df3db88b36d80d089f8aaffected · git
- dad0d04fa7ba41ce603a01e8e64967650303e9a2 and later · before 99129d80a5d4989ef8566f434f3589f60f28042baffected · git
- dad0d04fa7ba41ce603a01e8e64967650303e9a2 and later · before 31efbcff90884ea5f65bf3d1de01267db51ee3d1affected · git
- dad0d04fa7ba41ce603a01e8e64967650303e9a2 and later · before 4f431d88ea8093afc7ba55edf4652978c5a68f33affected · git
- before 3.15not affected · semver
- 5.10.249 and later · up to and including 5.10.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.162-1 | 6.1.162-1 |
| Debian:13 | linux | before 6.12.69-1 | 6.12.69-1 |
| Debian:14 | linux | before 6.18.8-1 | 6.18.8-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-23070Feb 4, 2026 · Octeontx2-af: Add proper checks for fwdata22Monitor
- ← EarlierCVE-2026-23071Feb 4, 2026 · regmap: Fix race condition in hwspinlock irqsave routine18Monitor
- Later →CVE-2026-23074Feb 4, 2026 · net/sched: Enforce that teql can only be used as root qdisc31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0d7c9e793e351cbbe9e06a9ca47d77b6ad288fb0 | Vendor (CNA) |
| Linux Linux | 31efbcff90884ea5f65bf3d1de01267db51ee3d1 | Vendor (CNA) |
| Linux Linux | 49ef094fdbc3526e5db2aebb404b84f79c5603dc | Vendor (CNA) |
| Linux Linux | 4f431d88ea8093afc7ba55edf4652978c5a68f33 | Vendor (CNA) |
| Linux Linux | 7761d7801f40e61069b4df3db88b36d80d089f8a | Vendor (CNA) |
| Linux Linux | 7c54d0c3e2cad4300be721ec2aecfcf8a63bc9f4 | Vendor (CNA) |
| Linux Linux | 99129d80a5d4989ef8566f434f3589f60f28042b | Vendor (CNA) |
| debian:linux | 6.1.162-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-787 · Out-of-bounds WriteCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/31efbcff90884ea5f65bf3d1de01267db51ee3d1
- git.kernel.org/stable/c/49ef094fdbc3526e5db2aebb404b84f79c5603dc
- git.kernel.org/stable/c/4f431d88ea8093afc7ba55edf4652978c5a68f33
- git.kernel.org/stable/c/7761d7801f40e61069b4df3db88b36d80d089f8a
- git.kernel.org/stable/c/7c54d0c3e2cad4300be721ec2aecfcf8a63bc9f4
- git.kernel.org/stable/c/99129d80a5d4989ef8566f434f3589f60f28042b
Vendor advisories and official records. Exploit/PoC links are deliberately left out.