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 90109 net sched fix 32 bit backlog wrap in gred bfifo
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-90109

net: sched: fix 32-bit backlog wrap in gred, bfifo and plug enqueueCVE-2026-90109

Answer in brief

CVE-2026-90109 records a Unknown severity vulnerability in net: sched: fix 32-bit backlog wrap in gred, bfifo and plug enqueue. 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 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
4 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). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Linux/Linuxgeneric>=a3eb95f891d6130b1fc03dd07a8b54cf0a5c8ab8 <3fb51b3960342bbee563543f8d33710fd0fb5a96 || >=a3eb95f891d6130b1fc03dd07a8b54cf0a5c8ab8 <8b2d8c70b969bf84f9e248bfaf2a7135129f2eb6 || >=a3eb95f891d6130b1fc03dd07a8b54cf0a5c8ab8 <d98b92f3d57976ae185238946ec5ea0be32195aa || >=a3eb95f891d6130b1fc03dd07a8b54cf0a5c8ab8 <4c660ee8c809637909f4f7eb1017f7b9401c75c43fb51b3960342bbee563543f8d33710fd0fb5a96, 8b2d8c70b969bf84f9e248bfaf2a7135129f2eb6, d98b92f3d57976ae185238946ec5ea0be32195aa, 4c660ee8c809637909f4f7eb1017f7b9401c75c4
Linux/Linuxgeneric4.2Not reported
Linux/Linuxgeneric>=a3eb95f891d6130b1fc03dd07a8b54cf0a5c8ab8 <c5ca77024812563fe15c4f7aa906791c3683e9fd || >=a3eb95f891d6130b1fc03dd07a8b54cf0a5c8ab8 <3fb51b3960342bbee563543f8d33710fd0fb5a96 || >=a3eb95f891d6130b1fc03dd07a8b54cf0a5c8ab8 <8b2d8c70b969bf84f9e248bfaf2a7135129f2eb6 || >=a3eb95f891d6130b1fc03dd07a8b54cf0a5c8ab8 <d98b92f3d57976ae185238946ec5ea0be32195aa || >=a3eb95f891d6130b1fc03dd07a8b54cf0a5c8ab8 <4c660ee8c809637909f4f7eb1017f7b9401c75c4c5ca77024812563fe15c4f7aa906791c3683e9fd, 3fb51b3960342bbee563543f8d33710fd0fb5a96, 8b2d8c70b969bf84f9e248bfaf2a7135129f2eb6, d98b92f3d57976ae185238946ec5ea0be32195aa, 4c660ee8c809637909f4f7eb1017f7b9401c75c4
Linux/Linuxgeneric>=a3eb95f891d6130b1fc03dd07a8b54cf0a5c8ab8 <771a1123570b487765bcf2d4cff3567e66bf1322 || >=a3eb95f891d6130b1fc03dd07a8b54cf0a5c8ab8 <c5ca77024812563fe15c4f7aa906791c3683e9fd || >=a3eb95f891d6130b1fc03dd07a8b54cf0a5c8ab8 <3fb51b3960342bbee563543f8d33710fd0fb5a96 || >=a3eb95f891d6130b1fc03dd07a8b54cf0a5c8ab8 <8b2d8c70b969bf84f9e248bfaf2a7135129f2eb6 || >=a3eb95f891d6130b1fc03dd07a8b54cf0a5c8ab8 <d98b92f3d57976ae185238946ec5ea0be32195aa || >=a3eb95f891d6130b1fc03dd07a8b54cf0a5c8ab8 <4c660ee8c809637909f4f7eb1017f7b9401c75c4771a1123570b487765bcf2d4cff3567e66bf1322, c5ca77024812563fe15c4f7aa906791c3683e9fd, 3fb51b3960342bbee563543f8d33710fd0fb5a96, 8b2d8c70b969bf84f9e248bfaf2a7135129f2eb6, d98b92f3d57976ae185238946ec5ea0be32195aa, 4c660ee8c809637909f4f7eb1017f7b9401c75c4

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 3fb51b3960342bbee563543f8d33710fd0fb5a96; Linux/Linux to c5ca77024812563fe15c4f7aa906791c3683e9fd; Linux/Linux to 771a1123570b487765bcf2d4cff3567e66bf1322 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: fix 32-bit backlog wrap in gred, bfifo and plug enqueue gred_enqueue(), bfifo_enqueue() and plug_enqueue() admit a packet when the current backlog plus the packet length fits within the queue limit: sch->qstats.backlog + qdisc_pkt_len(skb) <= sch->limit (gred default VQ) gred_backlog+qdisc_pkt_len(skb) <= q->limit (gred configured VQ) sch->qstats.backlog + qdisc_pkt_len(skb) <= sch->limit (bfifo) sch->qstats.backlog + skb->len <= q->limit (plug) sch->qstats.backlog and q->backlog are u32, and qdisc_pkt_len()/skb->len are unsigned int, so all sums are computed in 32 bits and wrap at 2^32. Once the true backlog exceeds 4 GiB the wrapped sum becomes small and admission keeps succeeding, so the queue grows without bound and the kernel can be driven to OOM. Promote the sums to u64 so admission stops once the true backlog exceeds the limit. The limit is u32, so the bounded queue stays below 2^32 and the stored u32 backlog never wraps. The bug can only be reproduced as root (albeit with ridiculous setup): attach a gred (or bfifo/plug) qdisc with a limit near 4 GiB, leaving the default VQ unconfigured (for gred), and drive >4 GiB of queued traffic (e.g. via a size table / stab to inflate qdisc_pkt_len, or sustained high-rate traffic). The u32 backlog+len sum wraps at 2^32, admission keeps succeeding, and the queue grows unboundedly to OOM.

Quoted source text, attributed separately from HOL analysis.