# CVE-2026-99100: wifi: p54: validate firmware record lengths


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** AZL-111164, BELL-CVE-2026-99100, DEBIAN-CVE-2026-99100, GHSA-m5mp-q9hj-5q22, UBUNTU-CVE-2026-99100

## What is CVE-2026-99100?

CVE-2026-99100 is a vulnerability in Linux, published on 28 Oct 2026. 

### Official description

In the Linux kernel, the following vulnerability has been resolved:

wifi: p54: validate firmware record lengths

The p54 firmware parser accesses component ID and component version
records without checking that their lengths cover the fields being read.
A malformed record can therefore make the parser read past the record.

Validate the component ID and component version record lengths before
accessing their data. The descriptor record is also checked against the
shortest descriptor length found in the supported firmware images.

Reject descriptor values that underflow the RX offset or produce an empty
RX range before updating the driver state.

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


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

Upgrade to a fixed version.

## Is CVE-2026-99100 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-99100 is a vulnerability in Linux, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-99100 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-99100/ (Markdown: https://insights.sbomify.com/CVE-2026-99100/index.md)
```

## Sources

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

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