CVE-2026-98186: wifi: mwifiex: bound the pairwise-cipher OUI walk to the IE length
Noroxi assessment
Priority: Monitor (action score 0/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.17% (FIRST EPSS).
- Fixed version: Linux Linux 2402c9e2644b7e10c7aaaf87bf12743d7e363559, 46cda9d42f0d6ec3057d878ddb1f38c0ab9f51df, 54a9cc5bd70b0d77a5069d4c46998c679a10c857; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1.
Low priority for now. Upgrade to Linux Linux 2402c9e2644b7e10c7aaaf87bf12743d7e363559, 46cda9d42f0d6ec3057d878ddb1f38c0ab9f51df, 54a9cc5bd70b0d77a5069d4c46998c679a10c857; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1 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: 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).
- Published
- Oct 6, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
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.
—
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.0affected
- 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e and later · before 77e642af7f2f6029e12a35c847c56cbd0466e799affected · git
- 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e and later · before 982b8fcdbb28f63bbbf02f0822c0bbda12ec27edaffected · git
- 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e and later · before 58767b41f87244eebaa5a475b9d276c83b89b933affected · git
- 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e and later · before 2402c9e2644b7e10c7aaaf87bf12743d7e363559affected · git
- 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e and later · before 54a9cc5bd70b0d77a5069d4c46998c679a10c857affected · git
- 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e and later · before 8bbef2b1ebfbadc0b9c37bbbf9c9e26fe2e41960affected · git
- 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e and later · before 46cda9d42f0d6ec3057d878ddb1f38c0ab9f51dfaffected · git
- 5e6e3a92b9a4c9416b17f468fa5c7fa2233b8b4e and later · before e667aee1c192d67d27c803007bfa9c6e0873e959affected · git
- before 3.0not 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.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.113-1~deb12u1 | 6.12.113-1~deb12u1 |
| Debian:13 | linux | before 6.12.113-1 | 6.12.113-1 |
| Debian:14 | linux | before 7.2.8-1 | 7.2.8-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-98184Oct 6, 2026 · wifi: mwifiex: prevent authentication frame length truncation0Monitor
- ← EarlierCVE-2026-98185Oct 6, 2026 · wifi: mwifiex: validate scan response extents0Monitor
- Later →CVE-2026-98187Oct 6, 2026 · wifi: p54: require a full exp_if record in PDR_INTERFACE_LIST0Monitor
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 | 2402c9e2644b7e10c7aaaf87bf12743d7e363559 | Vendor (CNA) |
| Linux Linux | 46cda9d42f0d6ec3057d878ddb1f38c0ab9f51df | Vendor (CNA) |
| Linux Linux | 54a9cc5bd70b0d77a5069d4c46998c679a10c857 | Vendor (CNA) |
| Linux Linux | 58767b41f87244eebaa5a475b9d276c83b89b933 | Vendor (CNA) |
| Linux Linux | 77e642af7f2f6029e12a35c847c56cbd0466e799 | Vendor (CNA) |
| Linux Linux | 8bbef2b1ebfbadc0b9c37bbbf9c9e26fe2e41960 | Vendor (CNA) |
| Linux Linux | 982b8fcdbb28f63bbbf02f0822c0bbda12ec27ed | Vendor (CNA) |
| Linux Linux | e667aee1c192d67d27c803007bfa9c6e0873e959 | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | 6.6.158.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.113-1 · Debian:13 | Package registry (OSV) |
| debian:linux | 7.2.8-1 · Debian:14 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.113-1~deb12u1 · 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.
- Published
- Fix recordedsame day
- TodayOct 30, 2026+24 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
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
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/46cda9d42f0d6ec3057d878ddb1f38c0ab9f51df
- git.kernel.org/stable/c/54a9cc5bd70b0d77a5069d4c46998c679a10c857
- git.kernel.org/stable/c/58767b41f87244eebaa5a475b9d276c83b89b933
- git.kernel.org/stable/c/77e642af7f2f6029e12a35c847c56cbd0466e799
- git.kernel.org/stable/c/8bbef2b1ebfbadc0b9c37bbbf9c9e26fe2e41960
- git.kernel.org/stable/c/982b8fcdbb28f63bbbf02f0822c0bbda12ec27ed
- git.kernel.org/stable/c/e667aee1c192d67d27c803007bfa9c6e0873e959
Vendor advisories and official records. Exploit/PoC links are deliberately left out.