HOL LogoGuard

Explore HOL

  • HOL home
  • AI agent registry
  • AI plugins
  • Open standards
  • HOL members
  • Sponsor HOL
  • Advertise with HOL

Guard product

  • Guard overviewLocal security and control for AI agents and the tools they use.
  • FeaturesRuntime protection, policy routing, review, and evidence.

Explore Guard

  • Product previewWalk through Guard surfaces in read-only demo mode.
  • ComparisonCompare Guard with native controls and AI security vendors.

AI tools

  • All AI toolsEvery supported AI tool and how Guard applies policy to it.
  • Codex
  • Claude Code
  • Cursor
  • Antigravity CLI
  • OpenCode
  • Hermes
  • OpenClaw
  • GitHub Copilot CLI
  • Antigravity
  • Kimi
  • Grok
  • Pi / Oh My Pi
  • Zcode

Extensions

  • All extensionsBrowse command and MCP coverage with owners and stated limits.
  • Command coverageShell command protection across clouds, databases, backups, and packages.
  • MCP server coverageSee how Guard maps risk state across MCP tools and servers.
  • Core safetyThe safety floor listings that ship with Guard.
  • Data and resilienceBackup and storage command protection.
  • Cloud and infrastructureAWS, Azure, GCP, Kubernetes, and more.

Security

  • AI security hubSecurity research, advisories, and agent safety coverage.
  • AI tool securitySecurity profiles for each supported coding agent.
  • Safe labsHands-on attack simulations with safe boundaries.
  • Redacted warningsReal blocked actions with sensitive details removed.
  • AdvisoriesCoordinated disclosure reports for AI tooling.
  • Active CVEsSearch active CVEs affecting AI tooling.

Learn

  • Security guidesPractical guides for securing AI agent workflows.
  • DocsInstall, configure, and operate Guard with confidence.
  • ResearchPublished security research, benchmarks, and methodology.

Community

  • ReleasesVersion history, shipped changes and upgrade notes.
  • ContributorsThe people and contributions behind HOL Guard.
  • AffiliatesShare Guard with your audience and earn from referrals.
  • SponsorFund agreed research, implementation and shared testing through the HOL Partner Program.
  • AdvertiseCompare README logo placements, previews and monthly prices, or promote a plugin or extension.
PricingEnterpriseOpen AppInstall Guard
  1. Guard
  2. Security
  3. CVEs
  4. CVE 2026 64571 wifi p54 validate rx frame length in
HOL Guard

Public security guidance for teams protecting AI harnesses, MCP servers, skills, prompts, and local tool execution.

Install Guard

AI Security

  • Prompt injection
  • MCP security
  • OWASP MCP mapping
  • Supply chain

Resources

  • Trust packet
  • Harness setup
  • Redacted warnings
  • Safe labs

Product

  • Install Guard
  • Pricing
  • Open dashboard
Guard
  • Guard Overview
  • Releases
  • Contributors
  • Install Guard
  • Pricing
Docs
  • Documentation Index
  • Developer Hub
  • API Reference
  • Root OpenAPI
  • Registry OpenAPI
  • Run in Postman
  • Standards
  • Submit ERC-8004 Contract
  • Feature Your Agent
Best Plugins
  • Browse Plugins
  • Plugin Launches
  • Best Claude Plugins
  • Best Codex Plugins
  • Best Grok Plugins
  • Best Kimi Plugins
  • Best DeepSeek Plugins
  • Best Antigravity Plugins
  • Best MCP Servers
  • Best Cursor Plugins
  • Best OpenCode Plugins
Best Agents
  • Best ERC-8004 Agents
  • Best Virtuals Agents
  • Best MCP Servers
  • Best A2A Agents
  • Best x402 Payable
  • All Categories
Community
  • Contribute to HOL
  • Telegram
  • X
More
  • About HOL
  • Sponsor
  • Advertise
  • Affiliate program
  • Contact
  • Blog
  • GitHub
  • Privacy
  • Terms of Service
Settings

Copyright © 2026 HOL DAO LLC. All rights reserved.

Back to active CVEs
Unknown severity · Source severity not reportedCVE-2026-64571

wifi: p54: validate RX frame length in p54_rx_eeprom_readback()CVE-2026-64571

Answer in brief

CVE-2026-64571 records a Unknown severity vulnerability in wifi: p54: validate RX frame length in p54_rx_eeprom_readback(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 5, 2026Updated Nov 3, 2026Source checked Nov 5, 2026First seen by HOL Aug 5, 2026Material review Nov 3, 2026
Upstream Advisory

Key facts

Risk
Unknown severitySource severity not reported
Exploitation
Not marked as known exploited
Affected software
3 mapped packages or products
Fix availability
Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Linux/Linuxgeneric>=7cb770729ba895f73253dfcd46c3fcba45d896f9 <25c3b85af3fc4f8043159b14e65790fc3bbdaf48 || >=7cb770729ba895f73253dfcd46c3fcba45d896f9 <f46f8f9c43fd02f4dd5f716d4bda296a523c04f0 || >=7cb770729ba895f73253dfcd46c3fcba45d896f9 <d38f5d868a0a4770e3bcd0925e16c46acdbc9509 || >=7cb770729ba895f73253dfcd46c3fcba45d896f9 <9096e1f7014174067239a63df18ae5f28301990d || >=7cb770729ba895f73253dfcd46c3fcba45d896f9 <ebd6d37fa94bee929e0b4c9ca19fdf9b1dcf6cea25c3b85af3fc4f8043159b14e65790fc3bbdaf48, f46f8f9c43fd02f4dd5f716d4bda296a523c04f0, d38f5d868a0a4770e3bcd0925e16c46acdbc9509, 9096e1f7014174067239a63df18ae5f28301990d, ebd6d37fa94bee929e0b4c9ca19fdf9b1dcf6cea
Linux/Linuxgeneric2.6.28Not reported
Linux/Linuxgeneric>=7cb770729ba895f73253dfcd46c3fcba45d896f9 <7a456ffcd20bd92ad0ef46c1aaa0e39e3be1f7e7 || >=7cb770729ba895f73253dfcd46c3fcba45d896f9 <88f7044f92b8326fbfab26d0d8ed297c367ebb76 || >=7cb770729ba895f73253dfcd46c3fcba45d896f9 <f21b7e096fe5371bf697cd410537fb434a763f5e || >=7cb770729ba895f73253dfcd46c3fcba45d896f9 <25c3b85af3fc4f8043159b14e65790fc3bbdaf48 || >=7cb770729ba895f73253dfcd46c3fcba45d896f9 <f46f8f9c43fd02f4dd5f716d4bda296a523c04f0 || >=7cb770729ba895f73253dfcd46c3fcba45d896f9 <d38f5d868a0a4770e3bcd0925e16c46acdbc9509 || >=7cb770729ba895f73253dfcd46c3fcba45d896f9 <9096e1f7014174067239a63df18ae5f28301990d || >=7cb770729ba895f73253dfcd46c3fcba45d896f9 <ebd6d37fa94bee929e0b4c9ca19fdf9b1dcf6cea7a456ffcd20bd92ad0ef46c1aaa0e39e3be1f7e7, 88f7044f92b8326fbfab26d0d8ed297c367ebb76, f21b7e096fe5371bf697cd410537fb434a763f5e, 25c3b85af3fc4f8043159b14e65790fc3bbdaf48, f46f8f9c43fd02f4dd5f716d4bda296a523c04f0, d38f5d868a0a4770e3bcd0925e16c46acdbc9509, 9096e1f7014174067239a63df18ae5f28301990d, ebd6d37fa94bee929e0b4c9ca19fdf9b1dcf6cea

Recommended response

  1. 1Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux, Linux/Linux.
  2. 2Review the reported fix. Update Linux/Linux to 25c3b85af3fc4f8043159b14e65790fc3bbdaf48; Linux/Linux to 7a456ffcd20bd92ad0ef46c1aaa0e39e3be1f7e7 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Aug 5, 2026

    Evidence: source:cvelist:source_dates:source-dates:record
  2. Source modified

    Nov 3, 2026

    Evidence: source:cvelist:source_dates:source-dates:record
  3. First seen by HOL

    Aug 5, 2026

Sources and claim methodology

  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
Upstream source description

In the Linux kernel, the following vulnerability has been resolved: wifi: p54: validate RX frame length in p54_rx_eeprom_readback() p54_rx_eeprom_readback() copies the requested EEPROM slice out of a device-supplied readback frame without checking that the skb actually holds that many bytes. Commit da1b9a55ff11 ("wifi: p54: prevent buffer-overflow in p54_rx_eeprom_readback()") closed the destination overflow by copying a fixed priv->eeprom_slice_size (and rejecting a mismatched advertised len), but the source side is still unbounded: nothing verifies the frame is long enough to supply that many bytes. A malicious USB device can send a short frame whose advertised len matches priv->eeprom_slice_size while the payload is truncated. The equality check passes and memcpy() reads past the end of the skb, leaking adjacent heap: BUG: KASAN: slab-out-of-bounds in p54_rx (drivers/net/wireless/intersil/p54/txrx.c:507) Read of size 1016 at addr ffff88800f077114 by task swapper/0/0 Call Trace: <IRQ> ... __asan_memcpy (mm/kasan/shadow.c:105) p54_rx (drivers/net/wireless/intersil/p54/txrx.c:507) p54u_rx_cb (drivers/net/wireless/intersil/p54/p54usb.c:163) __usb_hcd_giveback_urb (drivers/usb/core/hcd.c:1657) dummy_timer (drivers/usb/gadget/udc/dummy_hcd.c:2005) ... </IRQ> The buggy address belongs to the object at ffff88800f0770c0 which belongs to the cache skbuff_small_head of size 704 The buggy address is located 84 bytes inside of allocated 704-byte region [ffff88800f0770c0, ffff88800f077380) Check that the slice fits in the skb before copying.

Quoted source text, attributed separately from HOL analysis.

Record context

Vulnerability class
Tool Poisoning
EPSS
Not reported
CWE IDs
Not reported
Source
CVE List V5
Source checked
Nov 5, 2026
References
8 linked sources
Open source record