HOL LogoGuard

Explore HOL

  • HOL home
  • AI agent registry
  • AI plugins
  • Open standards
  • HOL members

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.
  • SponsorKeep agent security open: sponsor a project, place a banner, or fund a security initiative.
PricingEnterpriseOpen AppInstall Guard
  1. Guard
  2. Security
  3. CVEs
  4. CVE 2026 74623 net atlantic free stranded tx buffers on ring
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
  • 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-74623

net: atlantic: free stranded TX buffers on ring deinitCVE-2026-74623

Answer in brief

CVE-2026-74623 records a Unknown severity vulnerability in net: atlantic: free stranded TX buffers on ring deinit. 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 22, 2026Updated Aug 23, 2026Source checked Oct 7, 2026First seen by HOL Aug 22, 2026Material review Aug 23, 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>=eb36bedf28be6d986bdbcfa375bab08ffa45efd8 <307d80193b4a4a75b8dc4e0d3162be3755abbed7 || >=eb36bedf28be6d986bdbcfa375bab08ffa45efd8 <7a3e1481f4ee6c581bccc6bfc6c970aac5be7b0c || >=eb36bedf28be6d986bdbcfa375bab08ffa45efd8 <3447641d361dcc5511841d986ad4d849b2900d9b || >=eb36bedf28be6d986bdbcfa375bab08ffa45efd8 <b13202d401e1a20fec89b0cda733dcbaf279f79d || >=eb36bedf28be6d986bdbcfa375bab08ffa45efd8 <dd633280de7fdfd60dc4fcf63d04e2ad95b43269 || >=eb36bedf28be6d986bdbcfa375bab08ffa45efd8 <452636ea5410a96e02ebaaf80b21e3620b98e0dd307d80193b4a4a75b8dc4e0d3162be3755abbed7, 7a3e1481f4ee6c581bccc6bfc6c970aac5be7b0c, 3447641d361dcc5511841d986ad4d849b2900d9b, b13202d401e1a20fec89b0cda733dcbaf279f79d, dd633280de7fdfd60dc4fcf63d04e2ad95b43269, 452636ea5410a96e02ebaaf80b21e3620b98e0dd
Linux/Linuxgeneric4.11Not reported
Linux/Linuxgeneric>=eb36bedf28be6d986bdbcfa375bab08ffa45efd8 <a14ceebd13bf857bfca052bc5a6bd49e737912be || >=eb36bedf28be6d986bdbcfa375bab08ffa45efd8 <4f1c20873f70b4b22ef86dc38dad1fda8e169bcd || >=eb36bedf28be6d986bdbcfa375bab08ffa45efd8 <307d80193b4a4a75b8dc4e0d3162be3755abbed7 || >=eb36bedf28be6d986bdbcfa375bab08ffa45efd8 <7a3e1481f4ee6c581bccc6bfc6c970aac5be7b0c || >=eb36bedf28be6d986bdbcfa375bab08ffa45efd8 <3447641d361dcc5511841d986ad4d849b2900d9b || >=eb36bedf28be6d986bdbcfa375bab08ffa45efd8 <b13202d401e1a20fec89b0cda733dcbaf279f79d || >=eb36bedf28be6d986bdbcfa375bab08ffa45efd8 <dd633280de7fdfd60dc4fcf63d04e2ad95b43269 || >=eb36bedf28be6d986bdbcfa375bab08ffa45efd8 <452636ea5410a96e02ebaaf80b21e3620b98e0dda14ceebd13bf857bfca052bc5a6bd49e737912be, 4f1c20873f70b4b22ef86dc38dad1fda8e169bcd, 307d80193b4a4a75b8dc4e0d3162be3755abbed7, 7a3e1481f4ee6c581bccc6bfc6c970aac5be7b0c, 3447641d361dcc5511841d986ad4d849b2900d9b, b13202d401e1a20fec89b0cda733dcbaf279f79d, dd633280de7fdfd60dc4fcf63d04e2ad95b43269, 452636ea5410a96e02ebaaf80b21e3620b98e0dd

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

Evidence timeline and material changes

  1. Published upstream

    Aug 22, 2026

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

    Aug 23, 2026

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

    Aug 22, 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: net: atlantic: free stranded TX buffers on ring deinit aq_vec_deinit() drains the TX rings with a single aq_ring_tx_clean() call, which frees at most AQ_CFG_TX_CLEAN_BUDGET (256) descriptors and stops at hw_head, which no longer moves once aq_vec_stop() has stopped the hardware and NAPI. Completed descriptors beyond the budget and everything still posted in [hw_head, sw_tail) keep their skb or xdp_frame when the interface goes down: aq_vec_ring_free() then frees the buffer ring and the references are lost for good. Today this is a silent memory leak on every interface down under TX/XDP_TX load. With the conversion of the RX path to page_pool posted for net-next it becomes much more visible: XDP_TX frames carry fragment references on the RX ring's page_pool, so a single stranded frame keeps the pool's inflight count above zero forever. page_pool_destroy() then never completes, the pool is leaked together with its pages, and "page_pool_release_retry() stalled pool shutdown" is warned every 60 seconds from that point on, on every ifdown, XDP detach or ring resize under XDP_TX load. Bring back aq_ring_tx_deinit() as it was before the removal and use it for teardown again, with one extension: TX rings can hold xdp_frames nowadays, so release those too. They are returned with xdp_return_frame() since this runs in process context.

Quoted source text, attributed separately from HOL analysis.

Related CVEs

  • Gitea OAuth2 refresh token grant accepts access tokensSame generic ecosystem
  • Langflow OSS is affected by multiple vulnerabilitiesSame generic ecosystem
  • Langflow OSS is affected by multiple vulnerabilitiesSame generic ecosystem
  • Langflow OSS is affected by multiple vulnerabilitiesSame generic ecosystem
  • Langflow OSS is affected by multiple vulnerabilitiesSame generic ecosystem
  • Langflow OSS is affected by multiple vulnerabilitiesSame generic ecosystem

Record context

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