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 74631 net smc fix splice entry lifetime imbalance in
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
High ยท CVSS 8.4CVE-2026-74631

net: smc: fix splice entry lifetime imbalance in smc_rx_spliceCVE-2026-74631

Answer in brief

CVE-2026-74631 records a High severity (CVSS 8.4) vulnerability in net: smc: fix splice entry lifetime imbalance in smc_rx_splice. 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 25, 2026Source checked Oct 6, 2026First seen by HOL Aug 22, 2026Material review Aug 25, 2026
Upstream Advisory

Key facts

Risk
High ยท CVSS 8.4
Exploitation
Not marked as known exploited
Affected software
3 mapped packages or products
Fix availability
Available

Why this deserves its current priority

CVSS is 8.4. 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>=9014db202cb764b8e14c53e7bacc81f9a1a2ba7f <c841789e456ec6751342fa800639ce8e82ff0e6b || >=9014db202cb764b8e14c53e7bacc81f9a1a2ba7f <af02c67ce654356c58db20a0bb2db33ace3b07a8 || >=9014db202cb764b8e14c53e7bacc81f9a1a2ba7f <ca8342b5fc24c249fdb998468f6a168b457c67e5 || >=9014db202cb764b8e14c53e7bacc81f9a1a2ba7f <0b7d54cedea5cb158e21925ae0c6c2f5c87ed2a0 || >=9014db202cb764b8e14c53e7bacc81f9a1a2ba7f <4515c78f4d9fd577270f012efeb062ea58b3682d || >=9014db202cb764b8e14c53e7bacc81f9a1a2ba7f <5d9686af2976741bbd79b150d1c9e60b81e7f12ec841789e456ec6751342fa800639ce8e82ff0e6b, af02c67ce654356c58db20a0bb2db33ace3b07a8, ca8342b5fc24c249fdb998468f6a168b457c67e5, 0b7d54cedea5cb158e21925ae0c6c2f5c87ed2a0, 4515c78f4d9fd577270f012efeb062ea58b3682d, 5d9686af2976741bbd79b150d1c9e60b81e7f12e
Linux/Linuxgeneric4.18Not reported
Linux/Linuxgeneric>=9014db202cb764b8e14c53e7bacc81f9a1a2ba7f <7ddc7af2ae7fc5a0c0635b245c0824c8b76de5cb || >=9014db202cb764b8e14c53e7bacc81f9a1a2ba7f <07ad246529d136d5ef441d5ab4c305d132ff3090 || >=9014db202cb764b8e14c53e7bacc81f9a1a2ba7f <c841789e456ec6751342fa800639ce8e82ff0e6b || >=9014db202cb764b8e14c53e7bacc81f9a1a2ba7f <af02c67ce654356c58db20a0bb2db33ace3b07a8 || >=9014db202cb764b8e14c53e7bacc81f9a1a2ba7f <ca8342b5fc24c249fdb998468f6a168b457c67e5 || >=9014db202cb764b8e14c53e7bacc81f9a1a2ba7f <0b7d54cedea5cb158e21925ae0c6c2f5c87ed2a0 || >=9014db202cb764b8e14c53e7bacc81f9a1a2ba7f <4515c78f4d9fd577270f012efeb062ea58b3682d || >=9014db202cb764b8e14c53e7bacc81f9a1a2ba7f <5d9686af2976741bbd79b150d1c9e60b81e7f12e7ddc7af2ae7fc5a0c0635b245c0824c8b76de5cb, 07ad246529d136d5ef441d5ab4c305d132ff3090, c841789e456ec6751342fa800639ce8e82ff0e6b, af02c67ce654356c58db20a0bb2db33ace3b07a8, ca8342b5fc24c249fdb998468f6a168b457c67e5, 0b7d54cedea5cb158e21925ae0c6c2f5c87ed2a0, 4515c78f4d9fd577270f012efeb062ea58b3682d, 5d9686af2976741bbd79b150d1c9e60b81e7f12e

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 c841789e456ec6751342fa800639ce8e82ff0e6b; Linux/Linux to 7ddc7af2ae7fc5a0c0635b245c0824c8b76de5cb 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 25, 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: smc: fix splice entry lifetime imbalance in smc_rx_splice smc_rx_splice() passes pages to splice_to_pipe() before taking the references that cover the lifetime of each splice entry. In the VM-backed RMB path, splice_to_pipe() may drop unqueued entries through smc_rx_spd_release(), while queued entries are released later via the pipe buffer callback. The old post-splice accounting also derives the number of queued VM pages from an offset mutated while building the descriptor, and a multi-page splice pairs one sock_hold() with multiple sock_put() calls. Take the page and socket references for every candidate entry before splice_to_pipe(), and drop the matching private state, page reference, and socket reference from smc_rx_spd_release() for entries that never get queued. This fixes a refcount imbalance that can underflow page refcounts and trigger a use-after-free.

Quoted source text, attributed separately from HOL analysis.

Related CVEs

  • SPIP Crayons Plugin < 3.5.0 Authorization Bypass RCESame generic ecosystem
  • Payload: Order confirmation validation issue in Payload EcommerceSame generic ecosystem
  • Payload: Field access control bypass on auth collectionsSame generic ecosystem
  • Payload relationship-query authorization bypassSame generic ecosystem
  • Payload: Token refresh and password reset responses may expose restricted user fieldsSame generic ecosystem
  • Payload: ReDoS in Multipart Content-Type ValidationSame generic ecosystem

Record context

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