Skip to content
Noroxi
CVE.org (no NVD analysis yet)· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
  • Fixed version: Linux Linux 87a9aba92485889d510052e474999a6ec00b888c, 8c4f962f368d5e17481f3c2c5a43028953e137a5, 9af312d3607c8f9b5166a19cbf40cee351cc3a1d; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 Release Notes.

Low priority for now. Upgrade to Linux Linux 87a9aba92485889d510052e474999a6ec00b888c, 8c4f962f368d5e17481f3c2c5a43028953e137a5, 9af312d3607c8f9b5166a19cbf40cee351cc3a1d; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 Release Notes or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available
Published
Oct 28, 2026
Updated
Nov 1, 2026
EPSS
0.1% · 5th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-99100

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 2.6.24affected
    • eff1a59c48e3c6a006eb4fe5f2e405a996f2259d and later · before 87a9aba92485889d510052e474999a6ec00b888caffected · git
    • eff1a59c48e3c6a006eb4fe5f2e405a996f2259d and later · before d5c28994b2c1440480fccd0b6c2ce72c23bb9fffaffected · git
    • eff1a59c48e3c6a006eb4fe5f2e405a996f2259d and later · before 9af312d3607c8f9b5166a19cbf40cee351cc3a1daffected · git
    • eff1a59c48e3c6a006eb4fe5f2e405a996f2259d and later · before dda5245afc3470d70406764e3d9f5508e534920aaffected · git
    • eff1a59c48e3c6a006eb4fe5f2e405a996f2259d and later · before f4c6fcc2ad462ffd76d6e6f909bcd6ae0391f5b7affected · git
    • eff1a59c48e3c6a006eb4fe5f2e405a996f2259d and later · before f641066b0ddcd1b0cf007c0d04f9c966f6e888aeaffected · git
    • eff1a59c48e3c6a006eb4fe5f2e405a996f2259d and later · before 8c4f962f368d5e17481f3c2c5a43028953e137a5affected · git
    • eff1a59c48e3c6a006eb4fe5f2e405a996f2259d and later · before db7b86bd97b380ece8fa39cfdd7502a9fd35e56faffected · git
    • before 2.6.24not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxfrom 0—
Debian:13linuxbefore 6.12.115-26.12.115-2

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-99098Oct 26, 2026 · dm-integrity: fix buffer overflow in inline mode with large tag size
    0Monitor
  • ← EarlierCVE-2026-99099Oct 26, 2026 · x86/CPU/AMD: Fix AMD TLBI Erratum #1718
    31Monitor
  • Later →CVE-2026-99101Oct 28, 2026 · ntfs: move attribute payload before shrinking its record
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux87a9aba92485889d510052e474999a6ec00b888cVendor (CNA)
Linux Linux8c4f962f368d5e17481f3c2c5a43028953e137a5Vendor (CNA)
Linux Linux9af312d3607c8f9b5166a19cbf40cee351cc3a1dVendor (CNA)
Linux Linuxd5c28994b2c1440480fccd0b6c2ce72c23bb9fffVendor (CNA)
Linux Linuxdb7b86bd97b380ece8fa39cfdd7502a9fd35e56fVendor (CNA)
Linux Linuxdda5245afc3470d70406764e3d9f5508e534920aVendor (CNA)
Linux Linuxf4c6fcc2ad462ffd76d6e6f909bcd6ae0391f5b7Vendor (CNA)
Linux Linuxf641066b0ddcd1b0cf007c0d04f9c966f6e888aeVendor (CNA)
azl3 kernel 6.6.157.1-1 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
azl3 kernel 6.6.159.1-1 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
debian:linux6.12.115-2 · Debian:13Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. Fix recordedsame day
  3. TodayNov 5, 2026+8 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Exploit maturity— → none
  2. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records