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 2025 39810 bnxten fix memory corruption when fw resources
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
High · CVSS 7.8CVE-2025-39810

bnxt_en: Fix memory corruption when FW resources change during ifdownCVE-2025-39810

Answer in brief

CVE-2025-39810 records a High severity (CVSS 7.8) vulnerability in bnxt_en: Fix memory corruption when FW resources change during ifdown. 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). 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 16, 2025Updated Oct 30, 2026Source checked Nov 5, 2026First seen by HOL Aug 5, 2026Material review Oct 30, 2026
Upstream Advisory

Key facts

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

Why this deserves its current priority

CVSS is 7.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). Check affected ranges and fixed versions before updating.

Affected products and reported versions
ProductAffected versionsFixed versions
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:6.17:rc1:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:6.17:rc2:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:6.17:rc3:*:*:*:*:*:*Not reportedNot reported
Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Linux/Linuxgeneric>=ec5d31e3c15d5233b491400133c67f78a320062c <d00e98977ef519280b075d783653e2c492fffbb6 || >=ec5d31e3c15d5233b491400133c67f78a320062c <9ab6a9950f152e094395d2e3967f889857daa185 || >=ec5d31e3c15d5233b491400133c67f78a320062c <2747328ba2714f1a7454208dbbc1dc0631990b4ad00e98977ef519280b075d783653e2c492fffbb6, 9ab6a9950f152e094395d2e3967f889857daa185, 2747328ba2714f1a7454208dbbc1dc0631990b4a
Linux/Linuxgeneric5.4Not reported
Linux/Linuxgeneric>=ec5d31e3c15d5233b491400133c67f78a320062c <dc797a4bbbcac6d19e6e2508e4df685755cd94a5 || >=ec5d31e3c15d5233b491400133c67f78a320062c <d00e98977ef519280b075d783653e2c492fffbb6 || >=ec5d31e3c15d5233b491400133c67f78a320062c <9ab6a9950f152e094395d2e3967f889857daa185 || >=ec5d31e3c15d5233b491400133c67f78a320062c <2747328ba2714f1a7454208dbbc1dc0631990b4adc797a4bbbcac6d19e6e2508e4df685755cd94a5, d00e98977ef519280b075d783653e2c492fffbb6, 9ab6a9950f152e094395d2e3967f889857daa185, 2747328ba2714f1a7454208dbbc1dc0631990b4a
Linux/Linuxgeneric>=ec5d31e3c15d5233b491400133c67f78a320062c <c0082a8947cf1a543013346d10c1857f0c57db83 || >=ec5d31e3c15d5233b491400133c67f78a320062c <dc797a4bbbcac6d19e6e2508e4df685755cd94a5 || >=ec5d31e3c15d5233b491400133c67f78a320062c <d00e98977ef519280b075d783653e2c492fffbb6 || >=ec5d31e3c15d5233b491400133c67f78a320062c <9ab6a9950f152e094395d2e3967f889857daa185 || >=ec5d31e3c15d5233b491400133c67f78a320062c <2747328ba2714f1a7454208dbbc1dc0631990b4ac0082a8947cf1a543013346d10c1857f0c57db83, dc797a4bbbcac6d19e6e2508e4df685755cd94a5, d00e98977ef519280b075d783653e2c492fffbb6, 9ab6a9950f152e094395d2e3967f889857daa185, 2747328ba2714f1a7454208dbbc1dc0631990b4a

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 d00e98977ef519280b075d783653e2c492fffbb6; Linux/Linux to dc797a4bbbcac6d19e6e2508e4df685755cd94a5; Linux/Linux to c0082a8947cf1a543013346d10c1857f0c57db83 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Sep 16, 2025

    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

    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
Upstream source description

In the Linux kernel, the following vulnerability has been resolved: bnxt_en: Fix memory corruption when FW resources change during ifdown bnxt_set_dflt_rings() assumes that it is always called before any TC has been created. So it doesn't take bp->num_tc into account and assumes that it is always 0 or 1. In the FW resource or capability change scenario, the FW will return flags in bnxt_hwrm_if_change() that will cause the driver to reinitialize and call bnxt_cancel_reservations(). This will lead to bnxt_init_dflt_ring_mode() calling bnxt_set_dflt_rings() and bp->num_tc may be greater than 1. This will cause bp->tx_ring[] to be sized too small and cause memory corruption in bnxt_alloc_cp_rings(). Fix it by properly scaling the TX rings by bp->num_tc in the code paths mentioned above. Add 2 helper functions to determine bp->tx_nr_rings and bp->tx_nr_rings_per_tc.

Quoted source text, attributed separately from HOL analysis.

Record context

Vulnerability class
Memory Corruption
EPSS
Not reported
CWE IDs
CWE-787
Source
CVE List V5
Source checked
Nov 5, 2026
References
5 linked sources
Open source record