CVE-2026-98188
wifi: p54: validate curve data length in the calibration curve converters
No known exploitation. EPSS puts it in the 7th percentile. Fixed versions are out.
What to do
Find your product and version, then upgrade to the build on the right.
- LinuxAffected: ≥ eff1a59c48e3c6a006eb4fe5f2e405a996f2259d, < 81084c967c18233b19799a0c3352ebac043f31e2Upgrade to: 81084c967c18233b19799a0c3352ebac043f31e2Affected: ≥ eff1a59c48e3c6a006eb4fe5f2e405a996f2259d, < 41cdf14bf4b52fbe4673a172c2a6ad756cb08111Upgrade to: 41cdf14bf4b52fbe4673a172c2a6ad756cb08111Affected: ≥ eff1a59c48e3c6a006eb4fe5f2e405a996f2259d, < 03d313e3dfb49a44c10a5c423452967694fb85e2Upgrade to: 03d313e3dfb49a44c10a5c423452967694fb85e2Affected: ≥ eff1a59c48e3c6a006eb4fe5f2e405a996f2259d, < 42f4b03971f9d6329c4cbd1ea5155210d16ab65bUpgrade to: 42f4b03971f9d6329c4cbd1ea5155210d16ab65b + 4 more branchesStated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
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.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.2% chance of exploitation activity in the next 30 days, which ranks it in the 7th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
2 events over 0 days, from the signal feeds we watch.
- Publishedrecord updated
Affected products
Sources
References in the record
- git.kernel.org/stable/c/81084c967c18233b19799a0c3352ebac043f31e2
- git.kernel.org/stable/c/41cdf14bf4b52fbe4673a172c2a6ad756cb08111
- git.kernel.org/stable/c/03d313e3dfb49a44c10a5c423452967694fb85e2
And 5 more references. See all after sign-in
In the news
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Linux, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI