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-98188wifi: p54: validate curve data length in the calibration curve converters

Description

In the Linux kernel, the following vulnerability has been resolved: wifi: p54: validate curve data length in the calibration curve converters p54_convert_rev0() and p54_convert_rev1() read calibration curve data from the device-supplied EEPROM entry using channel and points-per-channel counts taken verbatim from that same entry, so an entry that declares more data than it carries drives an out-of-bounds read past the EEPROM buffer (verified with a KASAN reproducer of the conversion loop). The sibling converters p54_convert_output_limits() and p54_convert_db() already validate their counts against the entry length; this path was missed. Reject the entry when the counts do not fit in the entry data.

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 13 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.18% · 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 eff1a59c48e3c6a006eb4fe5f2e405a996f2259d – < 81084c967c18233b19799a0c3352ebac043f31e2
    • affected eff1a59c48e3c6a006eb4fe5f2e405a996f2259d – < 41cdf14bf4b52fbe4673a172c2a6ad756cb08111
    • affected eff1a59c48e3c6a006eb4fe5f2e405a996f2259d – < 03d313e3dfb49a44c10a5c423452967694fb85e2
    • affected eff1a59c48e3c6a006eb4fe5f2e405a996f2259d – < 42f4b03971f9d6329c4cbd1ea5155210d16ab65b
    • affected eff1a59c48e3c6a006eb4fe5f2e405a996f2259d – < 4d767d6f8753db22bfc14c2724bd9cee677ffb03
    • affected eff1a59c48e3c6a006eb4fe5f2e405a996f2259d – < 3bdcc4d61212b001b8752d80036509b4974ce16c
    • affected eff1a59c48e3c6a006eb4fe5f2e405a996f2259d – < b0c906107150b16925ee66da09127259864c7f36
    • affected eff1a59c48e3c6a006eb4fe5f2e405a996f2259d – < ce858fa6b8a214dee5adb82358885fa024cdd887
  • Linux · Linux

    • affected 2.6.24
    • unaffected < 2.6.24
    • 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.112 – ≤ 6.12.*
    • unaffected 6.18.54 – ≤ 6.18.*
    • unaffected 7.2.8 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .