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 90345 wifi brcmfmac fix p2p action frame handling
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
  • 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-90345

wifi: brcmfmac: fix P2P action frame handling without device vifCVE-2026-90345

Answer in brief

CVE-2026-90345 records a Unknown severity vulnerability in wifi: brcmfmac: fix P2P action frame handling without device vif. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.

Analysis pending evidence review

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

Published Sep 17, 2026Updated Oct 30, 2026Source checked Nov 1, 2026First seen by HOL Sep 17, 2026Material review Oct 30, 2026
Upstream Advisory

Record context

Vulnerability class
Vulnerability
EPSS
Not reported
CWE IDs
Not reported
Source
CVE List V5
Source checked
Nov 1, 2026
References
6 linked sources
Open source record

Key facts

Risk
Unknown severitySource severity not reported
Exploitation
Not marked as known exploited
Affected software
5 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), Linux/Linux (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Linux/Linuxgeneric>=6eda4e2c54255cd26a58d2fcec73ec3bff7a515b <f26e1b16904555e171292e183c3cfc1c38159fc5 || >=6eda4e2c54255cd26a58d2fcec73ec3bff7a515b <1b1edb9ebed49099bdc924cef49a9aea8b552199f26e1b16904555e171292e183c3cfc1c38159fc5, 1b1edb9ebed49099bdc924cef49a9aea8b552199
Linux/Linuxgeneric3.9Not reported
Linux/Linuxgeneric>=6eda4e2c54255cd26a58d2fcec73ec3bff7a515b <f334b26b884dff5d0a558dc464fa55f300868a68 || >=6eda4e2c54255cd26a58d2fcec73ec3bff7a515b <f26e1b16904555e171292e183c3cfc1c38159fc5 || >=6eda4e2c54255cd26a58d2fcec73ec3bff7a515b <1b1edb9ebed49099bdc924cef49a9aea8b552199f334b26b884dff5d0a558dc464fa55f300868a68, f26e1b16904555e171292e183c3cfc1c38159fc5, 1b1edb9ebed49099bdc924cef49a9aea8b552199
Linux/Linuxgeneric>=6eda4e2c54255cd26a58d2fcec73ec3bff7a515b <66b89c6a7da47efb38a9b839c2ae221b23a1c88b || >=6eda4e2c54255cd26a58d2fcec73ec3bff7a515b <6641ba636bf675b2634c49fe818931cf6ca8f547 || >=6eda4e2c54255cd26a58d2fcec73ec3bff7a515b <f334b26b884dff5d0a558dc464fa55f300868a68 || >=6eda4e2c54255cd26a58d2fcec73ec3bff7a515b <f26e1b16904555e171292e183c3cfc1c38159fc5 || >=6eda4e2c54255cd26a58d2fcec73ec3bff7a515b <1b1edb9ebed49099bdc924cef49a9aea8b55219966b89c6a7da47efb38a9b839c2ae221b23a1c88b, 6641ba636bf675b2634c49fe818931cf6ca8f547, f334b26b884dff5d0a558dc464fa55f300868a68, f26e1b16904555e171292e183c3cfc1c38159fc5, 1b1edb9ebed49099bdc924cef49a9aea8b552199
Linux/Linuxgeneric>=6eda4e2c54255cd26a58d2fcec73ec3bff7a515b <fb01b8c85682e531516adf6fb632bf2ccb67ec1d || >=6eda4e2c54255cd26a58d2fcec73ec3bff7a515b <66b89c6a7da47efb38a9b839c2ae221b23a1c88b || >=6eda4e2c54255cd26a58d2fcec73ec3bff7a515b <6641ba636bf675b2634c49fe818931cf6ca8f547 || >=6eda4e2c54255cd26a58d2fcec73ec3bff7a515b <f334b26b884dff5d0a558dc464fa55f300868a68 || >=6eda4e2c54255cd26a58d2fcec73ec3bff7a515b <f26e1b16904555e171292e183c3cfc1c38159fc5 || >=6eda4e2c54255cd26a58d2fcec73ec3bff7a515b <1b1edb9ebed49099bdc924cef49a9aea8b552199fb01b8c85682e531516adf6fb632bf2ccb67ec1d, 66b89c6a7da47efb38a9b839c2ae221b23a1c88b, 6641ba636bf675b2634c49fe818931cf6ca8f547, f334b26b884dff5d0a558dc464fa55f300868a68, f26e1b16904555e171292e183c3cfc1c38159fc5, 1b1edb9ebed49099bdc924cef49a9aea8b552199

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 f26e1b16904555e171292e183c3cfc1c38159fc5; Linux/Linux to f334b26b884dff5d0a558dc464fa55f300868a68; Linux/Linux to 66b89c6a7da47efb38a9b839c2ae221b23a1c88b; Linux/Linux to fb01b8c85682e531516adf6fb632bf2ccb67ec1d if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Sep 17, 2026

    Evidence: source:cvelist:source_dates:source-dates:record

  2. Source modified

    Oct 30, 2026

    Evidence: source:cvelist:source_dates:source-dates:record

  3. First seen by HOL

    Sep 17, 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
Upstream source description

In the Linux kernel, the following vulnerability has been resolved: wifi: brcmfmac: fix P2P action frame handling without device vif Some P2P action frame paths assume the P2P device vif is always available. That is not true when userspace sends non-P2P public action frames through the primary interface, or when action-frame abort runs after the P2P device vif has not been created. Fall back to the primary vif when aborting an action frame without a P2P device vif, and guard P2P device saved IE access before using it for peer channel search.

Quoted source text, attributed separately from HOL analysis.