CVE-2026-98186
wifi: mwifiex: bound the pairwise-cipher OUI walk to the IE length
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, < 77e642af7f2f6029e12a35c847c56cbd0466e799Upgrade to: 77e642af7f2f6029e12a35c847c56cbd0466e799Affected: ≥ 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e, < 982b8fcdbb28f63bbbf02f0822c0bbda12ec27edUpgrade to: 982b8fcdbb28f63bbbf02f0822c0bbda12ec27edAffected: ≥ 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e, < 58767b41f87244eebaa5a475b9d276c83b89b933Upgrade to: 58767b41f87244eebaa5a475b9d276c83b89b933Affected: ≥ 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e, < 2402c9e2644b7e10c7aaaf87bf12743d7e363559Upgrade to: 2402c9e2644b7e10c7aaaf87bf12743d7e363559 + 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: bound the pairwise-cipher OUI walk to the IE length mwifiex_search_oui_in_ie() reads a pairwise-cipher (PTK) count from a beacon/probe-response RSN or WPA information element and then walks that many 4-byte OUIs, comparing each with memcmp(). The count comes straight from the (attacker-supplied) IE and is never checked against the element's own length, and the callers admit the element on element_id alone (has_ieee_hdr() / has_vendor_hdr(), no length check). A crafted RSN/WPA IE with a large pairwise count therefore makes the walk read up to 255 * 4 bytes past the element -- an out-of-bounds read of the kmemdup()'d beacon buffer, reachable from any AP whose beacon/probe response is processed during scan-result parsing. Pass the number of IE bytes available at the OUI list and bound the walk to the element. Keep the length signed and reject a negative value before any unsigned arithmetic, so a small or zero IE length cannot underflow to a large size_t and defeat the bound. Found by 0sec automated security-research tooling (https://0sec.ai).
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/2402c9e2644b7e10c7aaaf87bf12743d7e363559
- git.kernel.org/stable/c/46cda9d42f0d6ec3057d878ddb1f38c0ab9f51df
- git.kernel.org/stable/c/54a9cc5bd70b0d77a5069d4c46998c679a10c857
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