CVE-2026-98185
wifi: mwifiex: validate scan response extents
No known exploitation. EPSS puts it in the 7th percentile. Fixed versions are out.
What to do
Find your product and version, then upgrade to the build on the right.
- LinuxAffected: ≥ 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e, < 25217c5f6ce0bf3004f80c129464cd35fe9a420fUpgrade to: 25217c5f6ce0bf3004f80c129464cd35fe9a420fAffected: ≥ 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e, < 48312f0085aa1577d6d41af2a079b34de17c1a57Upgrade to: 48312f0085aa1577d6d41af2a079b34de17c1a57Affected: ≥ 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e, < dccf5ecaad4d8d43c545921f20328e8f91af8698Upgrade to: dccf5ecaad4d8d43c545921f20328e8f91af8698Affected: ≥ 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e, < c4943323fda22ef27bb6479b9d328ae48c63f64cUpgrade to: c4943323fda22ef27bb6479b9d328ae48c63f64c + 4 more branchesStated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
In the Linux kernel, the following vulnerability has been resolved: wifi: mwifiex: validate scan response extents mwifiex_ret_802_11_scan() subtracts the fixed response fields and the firmware-provided BSS length from resp->size without first proving that either extent fits. A short response or oversized BSS length can therefore underflow tlv_buf_size and make the TLV parser walk beyond the command response. Compute the fixed extent from the selected normal or background scan response. Validate that the fixed fields and BSS data fit before deriving the TLV extent and entering the parser.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.2% chance of exploitation activity in the next 30 days, which ranks it in the 7th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
2 events over 0 days, from the signal feeds we watch.
- Publishedrecord updated
Affected products
Sources
References in the record
- git.kernel.org/stable/c/25217c5f6ce0bf3004f80c129464cd35fe9a420f
- git.kernel.org/stable/c/3687d7d48070838cc2953431b3a27717cab0aaf6
- git.kernel.org/stable/c/48312f0085aa1577d6d41af2a079b34de17c1a57
And 5 more references. See all after sign-in
In the news
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Linux, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI