CVE-2026-93803: wifi: libipw: fix key index receive bound checks
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 062840bdc9ee06169b3c371bf66711f1d7ec0bf4, 09d4a1bc3a08bb0e19bdf250b9f575cfef0bae82, 0b61c465ea62063593bc9ac186871b69e58ae991; 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 062840bdc9ee06169b3c371bf66711f1d7ec0bf4, 09d4a1bc3a08bb0e19bdf250b9f575cfef0bae82, 0b61c465ea62063593bc9ac186871b69e58ae991; 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: libipw: fix key index receive bound checks libipw_rx() reads skb->data[hdrlen + 3] to extract the WEP key index in both the software-decrypt key selection path and the hardware-decrypted IV/ICV strip path. In both places the existing guard only checks skb->len >= hdrlen + 3, which proves bytes up to hdrlen + 2 but not the byte at hdrlen + 3. Require hdrlen + 4 bytes before reading that item in both paths. This is a local source-boundary check only; it does not change the key index semantics.
- Published
- Sep 24, 2026
- Updated
- Oct 3, 2026
- EPSS
- 0.1% · 6th 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
- 2.6.14affected
- b453872c35cfcbdbf5a794737817f7d4e7b1b579 and later · before bb18262c19feb690ddde58c70e3ad04bc6fe566eaffected · git
- b453872c35cfcbdbf5a794737817f7d4e7b1b579 and later · before 09d4a1bc3a08bb0e19bdf250b9f575cfef0bae82affected · git
- b453872c35cfcbdbf5a794737817f7d4e7b1b579 and later · before 2836a870f612a8a6d9e390d00fa2cf6c90aa5808affected · git
- b453872c35cfcbdbf5a794737817f7d4e7b1b579 and later · before 0b61c465ea62063593bc9ac186871b69e58ae991affected · git
- b453872c35cfcbdbf5a794737817f7d4e7b1b579 and later · before 062840bdc9ee06169b3c371bf66711f1d7ec0bf4affected · git
- b453872c35cfcbdbf5a794737817f7d4e7b1b579 and later · before c54b643e9a0936d038921c547736574fd7382ceaaffected · git
- b453872c35cfcbdbf5a794737817f7d4e7b1b579 and later · before 74ed3669f26803b1761c1f55403062bea44c3466affected · git
- before 2.6.14not affected · semver
- 5.10.271 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.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-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-93801Sep 24, 2026 · smb/client: zero-initialize stack-allocated cifs_open_info_data28Monitor
- ← EarlierCVE-2026-93802Sep 24, 2026 · wifi: rsi: validate beacon length before fixed buffer copy0Monitor
- Later →CVE-2026-93804Sep 24, 2026 · wifi: mac80211: ibss: wait for in-flight TX on disconnect0Monitor
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 | 062840bdc9ee06169b3c371bf66711f1d7ec0bf4 | Vendor (CNA) |
| Linux Linux | 09d4a1bc3a08bb0e19bdf250b9f575cfef0bae82 | Vendor (CNA) |
| Linux Linux | 0b61c465ea62063593bc9ac186871b69e58ae991 | Vendor (CNA) |
| Linux Linux | 2836a870f612a8a6d9e390d00fa2cf6c90aa5808 | Vendor (CNA) |
| Linux Linux | 74ed3669f26803b1761c1f55403062bea44c3466 | Vendor (CNA) |
| Linux Linux | bb18262c19feb690ddde58c70e3ad04bc6fe566e | Vendor (CNA) |
| Linux Linux | c54b643e9a0936d038921c547736574fd7382cea | 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.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-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.
No dated events beyond publication.
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/09d4a1bc3a08bb0e19bdf250b9f575cfef0bae82
- git.kernel.org/stable/c/0b61c465ea62063593bc9ac186871b69e58ae991
- git.kernel.org/stable/c/2836a870f612a8a6d9e390d00fa2cf6c90aa5808
- git.kernel.org/stable/c/74ed3669f26803b1761c1f55403062bea44c3466
- git.kernel.org/stable/c/bb18262c19feb690ddde58c70e3ad04bc6fe566e
- git.kernel.org/stable/c/c54b643e9a0936d038921c547736574fd7382cea
Vendor advisories and official records. Exploit/PoC links are deliberately left out.