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 23385 netfilter nftables clone set on flush only
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
Medium ยท CVSS 5.5CVE-2026-23385

netfilter: nf_tables: clone set on flush onlyCVE-2026-23385

Answer in brief

CVE-2026-23385 records a Medium severity (CVSS 5.5) vulnerability in netfilter: nf_tables: clone set on flush only. 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) and additional mapped packages. Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Mar 25, 2026Updated Oct 30, 2026Source checked Nov 4, 2026First seen by HOL Aug 3, 2026Material review Oct 30, 2026
Upstream Advisory

Record context

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

Key facts

Risk
Medium ยท CVSS 5.5
Exploitation
Not marked as known exploited
Affected software
15 mapped packages or products
Fix availability
Available

Why this deserves its current priority

CVSS is 5.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) and additional mapped packages. 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:6.10:-:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:7.0:rc1:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:7.0:rc2:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:7.0:rc3:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:7.0:rc4:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:7.0:rc5:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:7.0:rc6:*:*:*:*:*:*Not reportedNot reported
cpe:2.3:o:linux:linux_kernel:7.0:rc7:*:*:*:*:*:*Not reportedNot reported
Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Linux/Linuxgeneric6.10Not reported
Linux/Linuxgeneric>=744dc9a47a8458ed49becd6123a092c7dae82b8b <e38f054f0af98224003e600545726fbd96379cfb || >=3f1d886cc7c3525d4dbeee24bfa9bb3fe0d48ddc <9154945a6394029822bd08c24cef5a3f86d0424a || >=3f1d886cc7c3525d4dbeee24bfa9bb3fe0d48ddc <b7f67282ca2be14b727dd698b50e10cf5d8c66f9 || >=3f1d886cc7c3525d4dbeee24bfa9bb3fe0d48ddc <fb7fb4016300ac622c964069e286dc83166a5d52 || 7c80229aa6e2707e59aa80cc041127cf9a79bcc9 || 11fb04a111934eb8fbed077cd943719ed16c6447 || >=6.6.148 <6.6.151 || >=5.15.217 <5.16 || >=6.1.184 <6.2e38f054f0af98224003e600545726fbd96379cfb, 9154945a6394029822bd08c24cef5a3f86d0424a, b7f67282ca2be14b727dd698b50e10cf5d8c66f9, fb7fb4016300ac622c964069e286dc83166a5d52, 6.6.151, 5.16, 6.2
Linux/Linuxgeneric>=3f1d886cc7c3525d4dbeee24bfa9bb3fe0d48ddc <9154945a6394029822bd08c24cef5a3f86d0424a || >=3f1d886cc7c3525d4dbeee24bfa9bb3fe0d48ddc <b7f67282ca2be14b727dd698b50e10cf5d8c66f9 || >=3f1d886cc7c3525d4dbeee24bfa9bb3fe0d48ddc <fb7fb4016300ac622c964069e286dc83166a5d52 || 744dc9a47a8458ed49becd6123a092c7dae82b8b || >=6.6.148 <6.79154945a6394029822bd08c24cef5a3f86d0424a, b7f67282ca2be14b727dd698b50e10cf5d8c66f9, fb7fb4016300ac622c964069e286dc83166a5d52, 6.7
Linux/Linuxgeneric>=744dc9a47a8458ed49becd6123a092c7dae82b8b <e38f054f0af98224003e600545726fbd96379cfb || >=3f1d886cc7c3525d4dbeee24bfa9bb3fe0d48ddc <9154945a6394029822bd08c24cef5a3f86d0424a || >=3f1d886cc7c3525d4dbeee24bfa9bb3fe0d48ddc <b7f67282ca2be14b727dd698b50e10cf5d8c66f9 || >=3f1d886cc7c3525d4dbeee24bfa9bb3fe0d48ddc <fb7fb4016300ac622c964069e286dc83166a5d52 || >=6.6.148 <6.6.151e38f054f0af98224003e600545726fbd96379cfb, 9154945a6394029822bd08c24cef5a3f86d0424a, b7f67282ca2be14b727dd698b50e10cf5d8c66f9, fb7fb4016300ac622c964069e286dc83166a5d52, 6.6.151
Linux/Linuxgeneric>=744dc9a47a8458ed49becd6123a092c7dae82b8b <e38f054f0af98224003e600545726fbd96379cfb || >=3f1d886cc7c3525d4dbeee24bfa9bb3fe0d48ddc <454306ceb94dc47a52443181082c91204c007a74 || >=3f1d886cc7c3525d4dbeee24bfa9bb3fe0d48ddc <9154945a6394029822bd08c24cef5a3f86d0424a || >=3f1d886cc7c3525d4dbeee24bfa9bb3fe0d48ddc <b7f67282ca2be14b727dd698b50e10cf5d8c66f9 || >=3f1d886cc7c3525d4dbeee24bfa9bb3fe0d48ddc <fb7fb4016300ac622c964069e286dc83166a5d52 || 7c80229aa6e2707e59aa80cc041127cf9a79bcc9 || 11fb04a111934eb8fbed077cd943719ed16c6447 || >=6.6.148 <6.6.151 || >=5.15.217 <5.16 || >=6.1.184 <6.2e38f054f0af98224003e600545726fbd96379cfb, 454306ceb94dc47a52443181082c91204c007a74, 9154945a6394029822bd08c24cef5a3f86d0424a, b7f67282ca2be14b727dd698b50e10cf5d8c66f9, fb7fb4016300ac622c964069e286dc83166a5d52, 6.6.151, 5.16, 6.2
Linux/Linuxgeneric>=11fb04a111934eb8fbed077cd943719ed16c6447 <9e63e1c2b171d30f5351b89b0a5d3926902f9ca6 || >=744dc9a47a8458ed49becd6123a092c7dae82b8b <e38f054f0af98224003e600545726fbd96379cfb || >=3f1d886cc7c3525d4dbeee24bfa9bb3fe0d48ddc <454306ceb94dc47a52443181082c91204c007a74 || >=3f1d886cc7c3525d4dbeee24bfa9bb3fe0d48ddc <9154945a6394029822bd08c24cef5a3f86d0424a || >=3f1d886cc7c3525d4dbeee24bfa9bb3fe0d48ddc <b7f67282ca2be14b727dd698b50e10cf5d8c66f9 || >=3f1d886cc7c3525d4dbeee24bfa9bb3fe0d48ddc <fb7fb4016300ac622c964069e286dc83166a5d52 || 7c80229aa6e2707e59aa80cc041127cf9a79bcc9 || >=6.1.184 <6.1.191 || >=6.6.148 <6.6.151 || >=5.15.217 <5.169e63e1c2b171d30f5351b89b0a5d3926902f9ca6, e38f054f0af98224003e600545726fbd96379cfb, 454306ceb94dc47a52443181082c91204c007a74, 9154945a6394029822bd08c24cef5a3f86d0424a, b7f67282ca2be14b727dd698b50e10cf5d8c66f9, fb7fb4016300ac622c964069e286dc83166a5d52, 6.1.191, 6.6.151, 5.16

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 e38f054f0af98224003e600545726fbd96379cfb; Linux/Linux to 9154945a6394029822bd08c24cef5a3f86d0424a; Linux/Linux to e38f054f0af98224003e600545726fbd96379cfb; Linux/Linux to e38f054f0af98224003e600545726fbd96379cfb; Linux/Linux to 9e63e1c2b171d30f5351b89b0a5d3926902f9ca6 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Mar 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

    Aug 3, 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: netfilter: nf_tables: clone set on flush only Syzbot with fault injection triggered a failing memory allocation with GFP_KERNEL which results in a WARN splat: iter.err WARNING: net/netfilter/nf_tables_api.c:845 at nft_map_deactivate+0x34e/0x3c0 net/netfilter/nf_tables_api.c:845, CPU#0: syz.0.17/5992 Modules linked in: CPU: 0 UID: 0 PID: 5992 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2026 RIP: 0010:nft_map_deactivate+0x34e/0x3c0 net/netfilter/nf_tables_api.c:845 Code: 8b 05 86 5a 4e 09 48 3b 84 24 a0 00 00 00 75 62 48 8d 65 d8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc cc e8 63 6d fa f7 90 <0f> 0b 90 43 +80 7c 35 00 00 0f 85 23 fe ff ff e9 26 fe ff ff 89 d9 RSP: 0018:ffffc900045af780 EFLAGS: 00010293 RAX: ffffffff89ca45bd RBX: 00000000fffffff4 RCX: ffff888028111e40 RDX: 0000000000000000 RSI: 00000000fffffff4 RDI: 0000000000000000 RBP: ffffc900045af870 R08: 0000000000400dc0 R09: 00000000ffffffff R10: dffffc0000000000 R11: fffffbfff1d141db R12: ffffc900045af7e0 R13: 1ffff920008b5f24 R14: dffffc0000000000 R15: ffffc900045af920 FS: 000055557a6a5500(0000) GS:ffff888125496000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fb5ea271fc0 CR3: 000000003269e000 CR4: 00000000003526f0 Call Trace: <TASK> __nft_release_table+0xceb/0x11f0 net/netfilter/nf_tables_api.c:12115 nft_rcv_nl_event+0xc25/0xdb0 net/netfilter/nf_tables_api.c:12187 notifier_call_chain+0x19d/0x3a0 kernel/notifier.c:85 blocking_notifier_call_chain+0x6a/0x90 kernel/notifier.c:380 netlink_release+0x123b/0x1ad0 net/netlink/af_netlink.c:761 __sock_release net/socket.c:662 [inline] sock_close+0xc3/0x240 net/socket.c:1455 Restrict set clone to the flush set command in the preparation phase. Add NFT_ITER_UPDATE_CLONE and use it for this purpose, update the rbtree and pipapo backends to only clone the set when this iteration type is used. As for the existing NFT_ITER_UPDATE type, update the pipapo backend to use the existing set clone if available, otherwise use the existing set representation. After this update, there is no need to clone a set that is being deleted, this includes bound anonymous set. An alternative approach to NFT_ITER_UPDATE_CLONE is to add a .clone interface and call it from the flush set path.

Quoted source text, attributed separately from HOL analysis.