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 64523 nethandshake take a long lived file reference at
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
Critical · CVSS 9.8CVE-2026-64523

net/handshake: Take a long-lived file reference at submitCVE-2026-64523

Answer in brief

CVE-2026-64523 records a Critical severity (CVSS 9.8) vulnerability in net/handshake: Take a long-lived file reference at submit. 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 Jul 25, 2026Updated Nov 3, 2026Source checked Nov 5, 2026First seen by HOL Aug 5, 2026Material review Nov 3, 2026
Upstream Advisory

Key facts

Risk
Critical · CVSS 9.8
Exploitation
Not marked as known exploited
Affected software
4 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), 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>=3b3009ea8abb713b022d94fba95ec270cf6e7eae <685b10dd0e32c7782cead16c8cf055c609678583 || >=3b3009ea8abb713b022d94fba95ec270cf6e7eae <16eaba5aa89c04eea125905bb8f988c1897f4f29 || >=3b3009ea8abb713b022d94fba95ec270cf6e7eae <09dba37eee70d0596e26645015f1aa95a9848e9d685b10dd0e32c7782cead16c8cf055c609678583, 16eaba5aa89c04eea125905bb8f988c1897f4f29, 09dba37eee70d0596e26645015f1aa95a9848e9d
Linux/Linuxgeneric6.4Not reported
Linux/Linuxgeneric>=3b3009ea8abb713b022d94fba95ec270cf6e7eae <685b10dd0e32c7782cead16c8cf055c609678583 || >=3b3009ea8abb713b022d94fba95ec270cf6e7eae <b913801ad9b9a51437d84d030ec6843e08976bd6 || >=3b3009ea8abb713b022d94fba95ec270cf6e7eae <16eaba5aa89c04eea125905bb8f988c1897f4f29 || >=3b3009ea8abb713b022d94fba95ec270cf6e7eae <09dba37eee70d0596e26645015f1aa95a9848e9d685b10dd0e32c7782cead16c8cf055c609678583, b913801ad9b9a51437d84d030ec6843e08976bd6, 16eaba5aa89c04eea125905bb8f988c1897f4f29, 09dba37eee70d0596e26645015f1aa95a9848e9d
Linux/Linuxgeneric>=3b3009ea8abb713b022d94fba95ec270cf6e7eae <22e371a93563c30ebebc576db049785e0d7fc617 || >=3b3009ea8abb713b022d94fba95ec270cf6e7eae <685b10dd0e32c7782cead16c8cf055c609678583 || >=3b3009ea8abb713b022d94fba95ec270cf6e7eae <b913801ad9b9a51437d84d030ec6843e08976bd6 || >=3b3009ea8abb713b022d94fba95ec270cf6e7eae <16eaba5aa89c04eea125905bb8f988c1897f4f29 || >=3b3009ea8abb713b022d94fba95ec270cf6e7eae <09dba37eee70d0596e26645015f1aa95a9848e9d22e371a93563c30ebebc576db049785e0d7fc617, 685b10dd0e32c7782cead16c8cf055c609678583, b913801ad9b9a51437d84d030ec6843e08976bd6, 16eaba5aa89c04eea125905bb8f988c1897f4f29, 09dba37eee70d0596e26645015f1aa95a9848e9d

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 685b10dd0e32c7782cead16c8cf055c609678583; Linux/Linux to 685b10dd0e32c7782cead16c8cf055c609678583; Linux/Linux to 22e371a93563c30ebebc576db049785e0d7fc617 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Jul 25, 2026

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

    Nov 3, 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: net/handshake: Take a long-lived file reference at submit handshake_nl_accept_doit() needs the file pointer backing req->hr_sk->sk_socket to survive the window between handshake_req_next() and the subsequent FD_PREPARE() and get_file(). The submit-side sock_hold() does not provide that. sk_refcnt keeps struct sock alive, but struct socket is owned by sock->file: when the consumer fputs the last file reference, sock_release() tears the socket down regardless of any sock_hold. Add an hr_file pointer to struct handshake_req and acquire an explicit reference on sock->file during handshake_req_submit(). handshake_complete() and handshake_req_cancel() release the reference on the completion-bit-winning path. The submit error path must also release the file reference, but after rhashtable insertion a concurrent handshake_req_cancel() can discover the request and race the error path. Gate the error-path cleanup -- sk_destruct restoration, fput, and request destruction -- with test_and_set_bit(HANDSHAKE_F_REQ_COMPLETED), the same serialization handshake_complete() and handshake_req_cancel() already use. When cancel has already claimed ownership, the submit error path returns without touching the request; socket teardown handles final destruction. The accept-side dereferences are not yet retargeted; that change comes in the next patch.

Quoted source text, attributed separately from HOL analysis.

Record context

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