Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-93803wifi: libipw: fix key index receive bound checks

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 9 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.17% · top 93% of all CVEs (16 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected b453872c35cfcbdbf5a794737817f7d4e7b1b579 – < bb18262c19feb690ddde58c70e3ad04bc6fe566e
    • affected b453872c35cfcbdbf5a794737817f7d4e7b1b579 – < 09d4a1bc3a08bb0e19bdf250b9f575cfef0bae82
    • affected b453872c35cfcbdbf5a794737817f7d4e7b1b579 – < 2836a870f612a8a6d9e390d00fa2cf6c90aa5808
    • affected b453872c35cfcbdbf5a794737817f7d4e7b1b579 – < 0b61c465ea62063593bc9ac186871b69e58ae991
    • affected b453872c35cfcbdbf5a794737817f7d4e7b1b579 – < 062840bdc9ee06169b3c371bf66711f1d7ec0bf4
    • affected b453872c35cfcbdbf5a794737817f7d4e7b1b579 – < c54b643e9a0936d038921c547736574fd7382cea
    • affected b453872c35cfcbdbf5a794737817f7d4e7b1b579 – < 74ed3669f26803b1761c1f55403062bea44c3466
  • Linux · Linux

    • affected 2.6.14
    • unaffected < 2.6.14
    • unaffected 5.10.271 – ≤ 5.10.*
    • unaffected 5.15.222 – ≤ 5.15.*
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.111 – ≤ 6.12.*
    • unaffected 6.18.53 – ≤ 6.18.*
    • unaffected 7.2 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-93803 badge
[![CVE-2026-93803](https://cveledger.app/badge/CVE-2026-93803.svg)](https://cveledger.app/cve/CVE-2026-93803)

Record last updated .