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 90099 netsched account classifier filter allocations to
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
Unknown severity · Source severity not reportedCVE-2026-90099

net/sched: account classifier filter allocations to memcgCVE-2026-90099

Answer in brief

CVE-2026-90099 records a Unknown severity vulnerability in net/sched: account classifier filter allocations to memcg. 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 Sep 17, 2026Updated Oct 30, 2026Source checked Nov 1, 2026First seen by HOL Sep 17, 2026Material review Oct 30, 2026
Upstream Advisory

Record context

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

Key facts

Risk
Unknown severitySource severity not reported
Exploitation
Not marked as known exploited
Affected software
5 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), Linux/Linux (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Linux/Linuxgeneric>=0da974f4f303a6842516b764507e3c0a03f41e5a <18c68c8f3d3ff0a4def1391021b439c4333a6c71 || >=0da974f4f303a6842516b764507e3c0a03f41e5a <1beb81947eb486716af80db7a584f9e9fef7e00318c68c8f3d3ff0a4def1391021b439c4333a6c71, 1beb81947eb486716af80db7a584f9e9fef7e003
Linux/Linuxgeneric2.6.18Not reported
Linux/Linuxgeneric>=0da974f4f303a6842516b764507e3c0a03f41e5a <68fb30607169c92de57c5c82b6af8a733af1cc09 || >=0da974f4f303a6842516b764507e3c0a03f41e5a <18c68c8f3d3ff0a4def1391021b439c4333a6c71 || >=0da974f4f303a6842516b764507e3c0a03f41e5a <1beb81947eb486716af80db7a584f9e9fef7e00368fb30607169c92de57c5c82b6af8a733af1cc09, 18c68c8f3d3ff0a4def1391021b439c4333a6c71, 1beb81947eb486716af80db7a584f9e9fef7e003
Linux/Linuxgeneric>=0da974f4f303a6842516b764507e3c0a03f41e5a <5fbb06d4f3d4c509ffe95572384a498bf319e5bf || >=0da974f4f303a6842516b764507e3c0a03f41e5a <bf6006cea193cf065f7a64fc7974247f8112af33 || >=0da974f4f303a6842516b764507e3c0a03f41e5a <68fb30607169c92de57c5c82b6af8a733af1cc09 || >=0da974f4f303a6842516b764507e3c0a03f41e5a <18c68c8f3d3ff0a4def1391021b439c4333a6c71 || >=0da974f4f303a6842516b764507e3c0a03f41e5a <1beb81947eb486716af80db7a584f9e9fef7e0035fbb06d4f3d4c509ffe95572384a498bf319e5bf, bf6006cea193cf065f7a64fc7974247f8112af33, 68fb30607169c92de57c5c82b6af8a733af1cc09, 18c68c8f3d3ff0a4def1391021b439c4333a6c71, 1beb81947eb486716af80db7a584f9e9fef7e003
Linux/Linuxgeneric>=0da974f4f303a6842516b764507e3c0a03f41e5a <8a622d5b4d81c1572f42bbf3fb823b6e63d44dae || >=0da974f4f303a6842516b764507e3c0a03f41e5a <5fbb06d4f3d4c509ffe95572384a498bf319e5bf || >=0da974f4f303a6842516b764507e3c0a03f41e5a <bf6006cea193cf065f7a64fc7974247f8112af33 || >=0da974f4f303a6842516b764507e3c0a03f41e5a <68fb30607169c92de57c5c82b6af8a733af1cc09 || >=0da974f4f303a6842516b764507e3c0a03f41e5a <18c68c8f3d3ff0a4def1391021b439c4333a6c71 || >=0da974f4f303a6842516b764507e3c0a03f41e5a <1beb81947eb486716af80db7a584f9e9fef7e0038a622d5b4d81c1572f42bbf3fb823b6e63d44dae, 5fbb06d4f3d4c509ffe95572384a498bf319e5bf, bf6006cea193cf065f7a64fc7974247f8112af33, 68fb30607169c92de57c5c82b6af8a733af1cc09, 18c68c8f3d3ff0a4def1391021b439c4333a6c71, 1beb81947eb486716af80db7a584f9e9fef7e003

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 18c68c8f3d3ff0a4def1391021b439c4333a6c71; Linux/Linux to 68fb30607169c92de57c5c82b6af8a733af1cc09; Linux/Linux to 5fbb06d4f3d4c509ffe95572384a498bf319e5bf; Linux/Linux to 8a622d5b4d81c1572f42bbf3fb823b6e63d44dae if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Sep 17, 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

    Sep 17, 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: net/sched: account classifier filter allocations to memcg Allocations in the tc classifier *_change() paths (filter objects, per-CPU counters, and per-filter aux data) use plain GFP_KERNEL without __GFP_ACCOUNT, allowing unprivileged users to pin kernel memory outside memcg charging. The shared tcf_exts_init_ex() action array allocation in cls_api.c was also uncharged; this patch closes it along with the per-classifier filter-object/percpu/aux allocations that remain unaccounted. Add GFP_KERNEL_ACCOUNT to: - the shared tcf_exts_init_ex() action array (cls_api.c), common to every filter of every classifier (32 pointers, 256 bytes); - the filter-object, per-CPU-counter, and per-filter aux allocations in cls_basic, cls_bpf, cls_cgroup, cls_flow, cls_flower, cls_fw, cls_matchall, cls_route and cls_u32; - the u32_init_knode() replace-path knode allocation (cls_u32.c), which allocates the same struct tc_u_knode + sel.keys on every replace of an existing knode and was missed by the create-path-only conversion. Also fix the cls_basic error path: basic_change() inserts fnew into the IDR before allocating the per-CPU counter. If alloc_percpu() fails the errout path kfree'd fnew without idr_remove, leaving a dangling pointer in the IDR. With GFP_KERNEL_ACCOUNT the percpu alloc becomes failable on demand (memcg at memory.max), making the dead path attacker-reachable and burning the handle permanently. Add the idr_remove on the percpu failure path, matching the basic_set_parms failure-path pattern. Note: [email protected] provided a poc for basic_cls, but it was easy to extend to the other classifiers. Conditions to recreate the bug: - CONFIG_NET_SCHED, CONFIG_NET_CLS_* (the classifier being used), CONFIG_NET_CLS_ACT, CONFIG_MEMCG, CONFIG_USER_NS, CONFIG_NET_NS. - Unprivileged user in a fresh user+network namespace (unshare -Urn), or root with CAP_NET_ADMIN. - Create a large number of tc filters (e.g. tc filter add dev lo ingress ... <classifier> ...) while watching a memcg-limited cgroup: system slab grows far faster than memory.current, pinning kernel memory outside memcg charging.

Quoted source text, attributed separately from HOL analysis.