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 80935 wifi mt76 mt7996 bound the device eeprom address
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
  • Contact
  • Blog
  • GitHub
  • Privacy
  • Terms of Service
Settings

Copyright © 2026 HOL DAO LLC. All rights reserved.

Back to active CVEs
High · CVSS 8.8CVE-2026-80935

wifi: mt76: mt7996: bound the device EEPROM address before the EFUSE copyCVE-2026-80935

Answer in brief

CVE-2026-80935 records a High severity (CVSS 8.8) vulnerability in wifi: mt76: mt7996: bound the device EEPROM address before the EFUSE copy. 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 11, 2026Updated Oct 21, 2026Source checked Oct 27, 2026First seen by HOL Sep 11, 2026Material review Oct 21, 2026
Upstream Advisory

Record context

Vulnerability class
Vulnerability
EPSS
Not reported
CWE IDs
Not reported
Source
CVE List V5
Source checked
Oct 27, 2026
References
5 linked sources
Open source record

Key facts

Risk
High · CVSS 8.8
Exploitation
Not marked as known exploited
Affected software
5 mapped packages or products
Fix availability
Available

Why this deserves its current priority

CVSS is 8.8. 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>=98686cd21624c75a043e96812beadddf4f6f48e5 <388f471ca4758f644394b681ce97677a4d0e772c || >=98686cd21624c75a043e96812beadddf4f6f48e5 <9e5abb5e2ade0b6fd0e47209711115d47a255176 || >=98686cd21624c75a043e96812beadddf4f6f48e5 <6be59da2063d5b3522bfde8aae0487ec095eb384 || >=98686cd21624c75a043e96812beadddf4f6f48e5 <13b3c29a782033ce4a230be9e5618032813dbcd4388f471ca4758f644394b681ce97677a4d0e772c, 9e5abb5e2ade0b6fd0e47209711115d47a255176, 6be59da2063d5b3522bfde8aae0487ec095eb384, 13b3c29a782033ce4a230be9e5618032813dbcd4
Linux/Linuxgeneric6.2Not reported
Linux/Linuxgeneric>=98686cd21624c75a043e96812beadddf4f6f48e5 <6be59da2063d5b3522bfde8aae0487ec095eb384 || >=98686cd21624c75a043e96812beadddf4f6f48e5 <13b3c29a782033ce4a230be9e5618032813dbcd46be59da2063d5b3522bfde8aae0487ec095eb384, 13b3c29a782033ce4a230be9e5618032813dbcd4
Linux/Linuxgeneric>=98686cd21624c75a043e96812beadddf4f6f48e5 <9e5abb5e2ade0b6fd0e47209711115d47a255176 || >=98686cd21624c75a043e96812beadddf4f6f48e5 <6be59da2063d5b3522bfde8aae0487ec095eb384 || >=98686cd21624c75a043e96812beadddf4f6f48e5 <13b3c29a782033ce4a230be9e5618032813dbcd49e5abb5e2ade0b6fd0e47209711115d47a255176, 6be59da2063d5b3522bfde8aae0487ec095eb384, 13b3c29a782033ce4a230be9e5618032813dbcd4
Linux/Linuxgeneric>=98686cd21624c75a043e96812beadddf4f6f48e5 <4892be1ef0bbe6db6b13bf46cb79b6706bb5b214 || >=98686cd21624c75a043e96812beadddf4f6f48e5 <388f471ca4758f644394b681ce97677a4d0e772c || >=98686cd21624c75a043e96812beadddf4f6f48e5 <9e5abb5e2ade0b6fd0e47209711115d47a255176 || >=98686cd21624c75a043e96812beadddf4f6f48e5 <6be59da2063d5b3522bfde8aae0487ec095eb384 || >=98686cd21624c75a043e96812beadddf4f6f48e5 <13b3c29a782033ce4a230be9e5618032813dbcd44892be1ef0bbe6db6b13bf46cb79b6706bb5b214, 388f471ca4758f644394b681ce97677a4d0e772c, 9e5abb5e2ade0b6fd0e47209711115d47a255176, 6be59da2063d5b3522bfde8aae0487ec095eb384, 13b3c29a782033ce4a230be9e5618032813dbcd4

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 388f471ca4758f644394b681ce97677a4d0e772c; Linux/Linux to 6be59da2063d5b3522bfde8aae0487ec095eb384; Linux/Linux to 9e5abb5e2ade0b6fd0e47209711115d47a255176; Linux/Linux to 4892be1ef0bbe6db6b13bf46cb79b6706bb5b214 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Sep 11, 2026

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

  2. Source modified

    Oct 21, 2026

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

  3. First seen by HOL

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

In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: mt7996: bound the device EEPROM address before the EFUSE copy mt7996_mcu_get_eeprom() derives the destination of the EFUSE/EXT block copy from the address reported by the MCU response (event->addr, a device-controlled __le32) and clamps only the copy length, never the destination offset into dev->mt76.eeprom.data. A malicious or malfunctioning device can report an arbitrary address and drive an out-of-bounds write of up to MT7996_EXT_EEPROM_BLOCK_SIZE bytes past eeprom.data. Reject a response whose address would place the copy outside eeprom.data before deriving the destination pointer. Devices that echo the requested in-bounds offset are unaffected.

Quoted source text, attributed separately from HOL analysis.