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 53229 netmlx5e xsk fix dma and xdpframe leak on xdptx
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.5CVE-2026-53229

net/mlx5e: xsk: Fix DMA and xdp_frame leak on XDP_TX xmit failureCVE-2026-53229

Answer in brief

CVE-2026-53229 records a High severity (CVSS 7.5) vulnerability in net/mlx5e: xsk: Fix DMA and xdp_frame leak on XDP_TX xmit failure. 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 Jun 25, 2026Updated Oct 30, 2026Source checked Nov 4, 2026First seen by HOL Jun 25, 2026Material review Oct 30, 2026
Upstream Advisory

Record context

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

Key facts

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

Why this deserves its current priority

CVSS is 7.5. 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:7.1:rc1:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:7.1:rc2:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:7.1:rc3:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:7.1:rc4:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:7.1:rc5:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:7.1:rc6:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:7.1:rc7:*:*:*:*:*:*Not reportedNot reported
Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Linux/Linuxgeneric>=84a0a2310d6de247335574649726cb000c7c0074 <7b3eeba50fbc3b45f279037c29a87a90e8bac1e1 || >=84a0a2310d6de247335574649726cb000c7c0074 <2789b74ae1f4b68333c9d5eec2f3354d07b16e61 || >=84a0a2310d6de247335574649726cb000c7c0074 <0aabca726b43d833721034e97d99efcc8237b22a || >=84a0a2310d6de247335574649726cb000c7c0074 <b69004f5a6ad32da84d8aa5b23b9c0caafe6252e7b3eeba50fbc3b45f279037c29a87a90e8bac1e1, 2789b74ae1f4b68333c9d5eec2f3354d07b16e61, 0aabca726b43d833721034e97d99efcc8237b22a, b69004f5a6ad32da84d8aa5b23b9c0caafe6252e
Linux/Linuxgeneric5.3Not reported
Linux/Linuxgeneric>=84a0a2310d6de247335574649726cb000c7c0074 <3bad189a31eb78575ea69f093e8ef5b7e3e8c832 || >=84a0a2310d6de247335574649726cb000c7c0074 <7b3eeba50fbc3b45f279037c29a87a90e8bac1e1 || >=84a0a2310d6de247335574649726cb000c7c0074 <2789b74ae1f4b68333c9d5eec2f3354d07b16e61 || >=84a0a2310d6de247335574649726cb000c7c0074 <0aabca726b43d833721034e97d99efcc8237b22a || >=84a0a2310d6de247335574649726cb000c7c0074 <b69004f5a6ad32da84d8aa5b23b9c0caafe6252e3bad189a31eb78575ea69f093e8ef5b7e3e8c832, 7b3eeba50fbc3b45f279037c29a87a90e8bac1e1, 2789b74ae1f4b68333c9d5eec2f3354d07b16e61, 0aabca726b43d833721034e97d99efcc8237b22a, b69004f5a6ad32da84d8aa5b23b9c0caafe6252e
Linux/Linuxgeneric>=84a0a2310d6de247335574649726cb000c7c0074 <bf0247d34d79d2740b3f1d6cc44dbd38ab2b169e || >=84a0a2310d6de247335574649726cb000c7c0074 <3bad189a31eb78575ea69f093e8ef5b7e3e8c832 || >=84a0a2310d6de247335574649726cb000c7c0074 <7b3eeba50fbc3b45f279037c29a87a90e8bac1e1 || >=84a0a2310d6de247335574649726cb000c7c0074 <2789b74ae1f4b68333c9d5eec2f3354d07b16e61 || >=84a0a2310d6de247335574649726cb000c7c0074 <0aabca726b43d833721034e97d99efcc8237b22a || >=84a0a2310d6de247335574649726cb000c7c0074 <b69004f5a6ad32da84d8aa5b23b9c0caafe6252ebf0247d34d79d2740b3f1d6cc44dbd38ab2b169e, 3bad189a31eb78575ea69f093e8ef5b7e3e8c832, 7b3eeba50fbc3b45f279037c29a87a90e8bac1e1, 2789b74ae1f4b68333c9d5eec2f3354d07b16e61, 0aabca726b43d833721034e97d99efcc8237b22a, b69004f5a6ad32da84d8aa5b23b9c0caafe6252e

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 7b3eeba50fbc3b45f279037c29a87a90e8bac1e1; Linux/Linux to 3bad189a31eb78575ea69f093e8ef5b7e3e8c832; Linux/Linux to bf0247d34d79d2740b3f1d6cc44dbd38ab2b169e if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Jun 25, 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

    Jun 25, 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: net/mlx5e: xsk: Fix DMA and xdp_frame leak on XDP_TX xmit failure In the XSK branch of mlx5e_xmit_xdp_buff(), when sq->xmit_xdp_frame() returns false (e.g. XDPSQ is full), the function returns without unmapping the DMA address or freeing the xdp_frame allocated by xdp_convert_zc_to_xdp_frame(). The xdpi_fifo push only happens on success, so the completion path cannot recover these entries. With CONFIG_DMA_API_DEBUG=y, the leak surfaces on driver unbind: DMA-API: pci 0000:08:00.0: device driver has pending DMA allocations while released from device [count=1116] One of leaked entries details: [device address=0x000000010ffd7028] [size=1534 bytes] [mapped with DMA_TO_DEVICE] [mapped as phy] WARNING: kernel/dma/debug.c:881 at dma_debug_device_change+0x127/0x180 ... DMA-API: Mapped at: debug_dma_map_phys+0x4b/0xd0 dma_map_phys+0xfd/0x2d0 mlx5e_xdp_handle+0x5ae/0xac0 [mlx5_core] mlx5e_xsk_skb_from_cqe_mpwrq_linear+0xc4/0x170 [mlx5_core] mlx5e_handle_rx_cqe_mpwrq+0xc1/0x290 [mlx5_core] Add the missing unmap + xdp_return_frame, matching the cleanup already done in mlx5e_xdp_xmit(). has_frags is rejected earlier in this branch, so no per-frag unmap is needed.

Quoted source text, attributed separately from HOL analysis.