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

> A missing length validation in the Linux kernel p54 WiFi driver allows an attacker with physical access to trigger an out-of-bounds read via a malicious EEPROM, potentially causing a crash or information leak.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-105999, BELL-CVE-2026-98188, DEBIAN-CVE-2026-98188, GHSA-4pxx-93w9-mj25, UBUNTU-CVE-2026-98188

## What is CVE-2026-98188?

CVE-2026-98188 is a memory corruption vulnerability in Linux, published on 6 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

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

## Which versions are affected by CVE-2026-98188?


## How do I fix CVE-2026-98188?

Apply the vendor's patch.

## Is CVE-2026-98188 being exploited?

There is no known exploitation of CVE-2026-98188 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-98188 and fix it if it is affected.

What it is: CVE-2026-98188 is a memory corruption vulnerability in Linux, published on 6 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-98188 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-98188/ (Markdown: https://insights.sbomify.com/CVE-2026-98188/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-98188
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-98188
- OSV: https://osv.dev/vulnerability/CVE-2026-98188

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-98188/
Summaries are generated and may contain mistakes; the official description above is the record.