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 2021 47587 net systemport add global locking for descriptor
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
Critical ยท CVSS 9.8CVE-2021-47587

net: systemport: Add global locking for descriptor lifecycleCVE-2021-47587

Answer in brief

CVE-2021-47587 records a Critical severity (CVSS 9.8) vulnerability in net: systemport: Add global locking for descriptor lifecycle. The current sources do not mark it as known exploited. The current feed maps 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 19, 2024Updated Aug 5, 2026Source checked Nov 3, 2026First seen by HOL Aug 4, 2026Material review Aug 5, 2026
Upstream Advisory

Key facts

Risk
Critical ยท CVSS 9.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 9.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). 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:5.16:rc1:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:5.16:rc2:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:5.16:rc3:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:5.16:rc4:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:5.16:rc5:*:*:*:*:*:*Not reportedNot reported
Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Linux/Linuxgeneric3.16Not reported
Linux/Linuxgeneric>=80105befdb4b8cea924711b40b2462b87df65b62 <8ed2f5d08d6e59f8c78b2869bfb95d0be32c094c || >=80105befdb4b8cea924711b40b2462b87df65b62 <de57f62f76450b934de8203711bdc4f7953c3421 || >=80105befdb4b8cea924711b40b2462b87df65b62 <f3fde37d3f0d429f0fcce214cb52588a9e21260e || >=80105befdb4b8cea924711b40b2462b87df65b62 <595a684fa6f23b21958379a18cfa83862c73c2e1 || >=80105befdb4b8cea924711b40b2462b87df65b62 <c675256a7f131f5ba3f331efb715e8f31ea0e392 || >=80105befdb4b8cea924711b40b2462b87df65b62 <6e1011cd183faae8daff275c72444edcdfe0d473 || >=80105befdb4b8cea924711b40b2462b87df65b62 <eb4687c7442942e115420a30185f8d83faf37696 || >=80105befdb4b8cea924711b40b2462b87df65b62 <8b8e6e782456f1ce02a7ae914bbd5b1053f0b0348ed2f5d08d6e59f8c78b2869bfb95d0be32c094c, de57f62f76450b934de8203711bdc4f7953c3421, f3fde37d3f0d429f0fcce214cb52588a9e21260e, 595a684fa6f23b21958379a18cfa83862c73c2e1, c675256a7f131f5ba3f331efb715e8f31ea0e392, 6e1011cd183faae8daff275c72444edcdfe0d473, eb4687c7442942e115420a30185f8d83faf37696, 8b8e6e782456f1ce02a7ae914bbd5b1053f0b034

Recommended response

  1. 1Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
  2. 2Review the reported fix. Update Linux/Linux to 8ed2f5d08d6e59f8c78b2869bfb95d0be32c094c if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Jun 19, 2024

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

    Aug 5, 2026

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

    Aug 4, 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: systemport: Add global locking for descriptor lifecycle The descriptor list is a shared resource across all of the transmit queues, and the locking mechanism used today only protects concurrency across a given transmit queue between the transmit and reclaiming. This creates an opportunity for the SYSTEMPORT hardware to work on corrupted descriptors if we have multiple producers at once which is the case when using multiple transmit queues. This was particularly noticeable when using multiple flows/transmit queues and it showed up in interesting ways in that UDP packets would get a correct UDP header checksum being calculated over an incorrect packet length. Similarly TCP packets would get an equally correct checksum computed by the hardware over an incorrect packet length. The SYSTEMPORT hardware maintains an internal descriptor list that it re-arranges when the driver produces a new descriptor anytime it writes to the WRITE_PORT_{HI,LO} registers, there is however some delay in the hardware to re-organize its descriptors and it is possible that concurrent TX queues eventually break this internal allocation scheme to the point where the length/status part of the descriptor gets used for an incorrect data buffer. The fix is to impose a global serialization for all TX queues in the short section where we are writing to the WRITE_PORT_{HI,LO} registers which solves the corruption even with multiple concurrent TX queues being used.

Quoted source text, attributed separately from HOL analysis.

Related CVEs

  • io-wq: order the exit bit against worker creation task workSame linux/linux package
  • pid_namespace: prevent TIF_NOTIFY_SIGNAL from interrupting the reaperSame linux/linux package
  • KEYS: Fix key_reject_and_link() race with keyring restrictionSame linux/linux package
  • tipc: protect node reset trace dump with node lockSame linux/linux package
  • tracing: Do not initialize tracefs work if tracing is disabledSame linux/linux package
  • i2c: xiic: restore non-managed runtime PM to fix clk WARN floodSame linux/linux package

Record context

Vulnerability class
Vulnerability
EPSS
Not reported
CWE IDs
CWE-667
Source
CVE List V5
Source checked
Nov 3, 2026
References
8 linked sources
Open source record