CVE-2026-98186 — wifi: mwifiex: bound the pairwise-cipher OUI walk to the IE length
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).
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e and < 77e642af7f2f6029e12a35c847c56cbd0466e799≥ 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e and < 982b8fcdbb28f63bbbf02f0822c0bbda12ec27ed≥ 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e and < 58767b41f87244eebaa5a475b9d276c83b89b933≥ 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e and < 2402c9e2644b7e10c7aaaf87bf12743d7e363559≥ 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e and < 54a9cc5bd70b0d77a5069d4c46998c679a10c857≥ 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e and < 8bbef2b1ebfbadc0b9c37bbbf9c9e26fe2e41960≥ 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e and < 46cda9d42f0d6ec3057d878ddb1f38c0ab9f51df≥ 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e and < e667aee1c192d67d27c803007bfa9c6e0873e959 and 1 moreversion 3.0 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.18%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
8 on the record
- git.kernel.org/stable/c/54a9cc5bd70b0d77a5069d4c46998c679a10c857
- git.kernel.org/stable/c/46cda9d42f0d6ec3057d878ddb1f38c0ab9f51df
- git.kernel.org/stable/c/2402c9e2644b7e10c7aaaf87bf12743d7e363559
- git.kernel.org/stable/c/58767b41f87244eebaa5a475b9d276c83b89b933
- git.kernel.org/stable/c/e667aee1c192d67d27c803007bfa9c6e0873e959
- git.kernel.org/stable/c/8bbef2b1ebfbadc0b9c37bbbf9c9e26fe2e41960
- git.kernel.org/stable/c/982b8fcdbb28f63bbbf02f0822c0bbda12ec27ed
- git.kernel.org/stable/c/77e642af7f2f6029e12a35c847c56cbd0466e799
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 9h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 9h
- Unknown CVE-2026-98431 RDMA/uverbs: Fix mmap_lock/disassociation_lock circular dependency 1d
- Unknown CVE-2026-98430 RDMA/efa: Keep admin queues alive while IRQ is registered 1d
- Unknown CVE-2026-98429 RDMA/efa: Keep EQ resources alive while IRQ is registered 1d
- Unknown CVE-2026-98428 ALSA: usb: 6fire: Avoid embedded URBs 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-98186 is "wifi: mwifiex: bound the pairwise-cipher OUI walk to the IE length", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.18% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.