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 90182 blk iocost clear delay state when freeing policy
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-90182

blk-iocost: clear delay state when freeing policy dataCVE-2026-90182

Answer in brief

CVE-2026-90182 records a Unknown severity vulnerability in blk-iocost: clear delay state when freeing policy data. 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>=7caa47151ab2e644dd221f741ec7578d9532c9a3 <b9c16db833e3ff15d923282f94dddf0e10fab8c0 || >=7caa47151ab2e644dd221f741ec7578d9532c9a3 <97cb95d2148835ae86ff916b145aef332d40439db9c16db833e3ff15d923282f94dddf0e10fab8c0, 97cb95d2148835ae86ff916b145aef332d40439d
Linux/Linuxgeneric5.4Not reported
Linux/Linuxgeneric>=7caa47151ab2e644dd221f741ec7578d9532c9a3 <b399a88eb8b16c5a1a3645fd49ff507fb82b363c || >=7caa47151ab2e644dd221f741ec7578d9532c9a3 <b9c16db833e3ff15d923282f94dddf0e10fab8c0 || >=7caa47151ab2e644dd221f741ec7578d9532c9a3 <97cb95d2148835ae86ff916b145aef332d40439db399a88eb8b16c5a1a3645fd49ff507fb82b363c, b9c16db833e3ff15d923282f94dddf0e10fab8c0, 97cb95d2148835ae86ff916b145aef332d40439d
Linux/Linuxgeneric>=7caa47151ab2e644dd221f741ec7578d9532c9a3 <6b59f976db5def818829fc1eb4efc0a5c8c2f0cf || >=7caa47151ab2e644dd221f741ec7578d9532c9a3 <8b4d0b1b3079bbe9a5366e2c8020eb22926733b6 || >=7caa47151ab2e644dd221f741ec7578d9532c9a3 <b399a88eb8b16c5a1a3645fd49ff507fb82b363c || >=7caa47151ab2e644dd221f741ec7578d9532c9a3 <b9c16db833e3ff15d923282f94dddf0e10fab8c0 || >=7caa47151ab2e644dd221f741ec7578d9532c9a3 <97cb95d2148835ae86ff916b145aef332d40439d6b59f976db5def818829fc1eb4efc0a5c8c2f0cf, 8b4d0b1b3079bbe9a5366e2c8020eb22926733b6, b399a88eb8b16c5a1a3645fd49ff507fb82b363c, b9c16db833e3ff15d923282f94dddf0e10fab8c0, 97cb95d2148835ae86ff916b145aef332d40439d
Linux/Linuxgeneric>=7caa47151ab2e644dd221f741ec7578d9532c9a3 <6942cb740fb17b24731728b25994eba361776011 || >=7caa47151ab2e644dd221f741ec7578d9532c9a3 <6b59f976db5def818829fc1eb4efc0a5c8c2f0cf || >=7caa47151ab2e644dd221f741ec7578d9532c9a3 <8b4d0b1b3079bbe9a5366e2c8020eb22926733b6 || >=7caa47151ab2e644dd221f741ec7578d9532c9a3 <b399a88eb8b16c5a1a3645fd49ff507fb82b363c || >=7caa47151ab2e644dd221f741ec7578d9532c9a3 <b9c16db833e3ff15d923282f94dddf0e10fab8c0 || >=7caa47151ab2e644dd221f741ec7578d9532c9a3 <97cb95d2148835ae86ff916b145aef332d40439d6942cb740fb17b24731728b25994eba361776011, 6b59f976db5def818829fc1eb4efc0a5c8c2f0cf, 8b4d0b1b3079bbe9a5366e2c8020eb22926733b6, b399a88eb8b16c5a1a3645fd49ff507fb82b363c, b9c16db833e3ff15d923282f94dddf0e10fab8c0, 97cb95d2148835ae86ff916b145aef332d40439d

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 b9c16db833e3ff15d923282f94dddf0e10fab8c0; Linux/Linux to b399a88eb8b16c5a1a3645fd49ff507fb82b363c; Linux/Linux to 6b59f976db5def818829fc1eb4efc0a5c8c2f0cf; Linux/Linux to 6942cb740fb17b24731728b25994eba361776011 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: blk-iocost: clear delay state when freeing policy data iocg_kick_delay() turns sufficiently large debt into an explicit block-cgroup delay with blkcg_set_delay(), setting blkg->use_delay to -1 and incrementing blkcg->congestion_count. Clearing it again depends on iocg_kick_delay() running from the period timer, the waitq timer or the issue path. ioc_pd_free() removes the iocg from active_iocgs and cancels its waitq timer, and no further bios can arrive, so once it has run nothing is left which can reduce the debt and clear the delay. The blkcg stays marked congested for the rest of its life. blk_cgroup_congested() then returns true for every task in that cgroup and its descendants: page_cache_sync_ra() cuts readahead to a single page, page_cache_async_ra() skips it altogether, and __folio_throttle_swaprate() takes swap_avail_lock and schedules a throttle on anonymous folio allocation. Clear it explicitly, after the list removal and the synchronous hrtimer_cancel() so that neither timer processing nor an I/O path can re-arm it. The free callback can also see policy data which was never attached to a blkg, hence the pd->blkg check.

Quoted source text, attributed separately from HOL analysis.