HOL LogoGuard

Explore HOL

  • HOL home
  • AI agent registry
  • AI plugins
  • Open standards
  • HOL members

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.
  • SponsorKeep agent security open: sponsor a project, place a banner, or fund a security initiative.
PricingEnterpriseOpen AppInstall Guard
  1. Guard
  2. Security
  3. CVEs
  4. CVE 2026 74594 schedpsi shut down rtpolltimer in psicgroupfree
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
  • Contact
  • Blog
  • GitHub
  • Privacy
  • Terms of Service
Settings

Copyright ยฉ 2026 HOL DAO LLC. All rights reserved.

Back to active CVEs
High ยท CVSS 7.8CVE-2026-74594

sched/psi: Shut down rtpoll_timer in psi_cgroup_free()CVE-2026-74594

Answer in brief

CVE-2026-74594 records a High severity (CVSS 7.8) vulnerability in sched/psi: Shut down rtpoll_timer in psi_cgroup_free(). The current sources do not mark it as known exploited. The current feed maps 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 Aug 22, 2026Updated Aug 25, 2026Source checked Oct 7, 2026First seen by HOL Aug 22, 2026Material review Aug 25, 2026
Upstream Advisory

Key facts

Risk
High ยท CVSS 7.8
Exploitation
Not marked as known exploited
Affected software
3 mapped packages or products
Fix availability
Available

Why this deserves its current priority

CVSS is 7.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). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Linux/Linuxgeneric>=8f91efd870ea5d8bc10b0fcc9740db51cd4c0c83 <1e5ca82eee59caca6988f9d6e859786aab8a5fa0 || >=8f91efd870ea5d8bc10b0fcc9740db51cd4c0c83 <310b5a537a78c358a4cd244bd767c1a517a05459 || >=8f91efd870ea5d8bc10b0fcc9740db51cd4c0c83 <806fcff98c1d7cb3c1dc0015e55ebdbe819e6b08 || >=8f91efd870ea5d8bc10b0fcc9740db51cd4c0c83 <8037c5b2b2a447df52542f4d8535895d837bdcbd || >=8f91efd870ea5d8bc10b0fcc9740db51cd4c0c83 <611e7821c4f83a671455658797336faecc3a5196 || >=8f91efd870ea5d8bc10b0fcc9740db51cd4c0c83 <5457025fa8ca3c0d2732109513de839e3e797190 || 6bfcb6178925b1fd28c102e53d403091b8f49396 || e1e5e263bbe0e6e9c3db36aa48a3c8acf546fa49 || 979965c33f734a1666af67900408f997ac669c23 || >=5.10.50 <5.11 || >=5.12.17 <5.13 || >=5.13.2 <5.141e5ca82eee59caca6988f9d6e859786aab8a5fa0, 310b5a537a78c358a4cd244bd767c1a517a05459, 806fcff98c1d7cb3c1dc0015e55ebdbe819e6b08, 8037c5b2b2a447df52542f4d8535895d837bdcbd, 611e7821c4f83a671455658797336faecc3a5196, 5457025fa8ca3c0d2732109513de839e3e797190, 5.11, 5.13, 5.14
Linux/Linuxgeneric5.14Not reported
Linux/Linuxgeneric>=6bfcb6178925b1fd28c102e53d403091b8f49396 <4addb102154b7cf6e2310ccbe20c3c08619e520d || >=8f91efd870ea5d8bc10b0fcc9740db51cd4c0c83 <894a9300d7fb2e2951da92e565ae6de7ddfb0a69 || >=8f91efd870ea5d8bc10b0fcc9740db51cd4c0c83 <1e5ca82eee59caca6988f9d6e859786aab8a5fa0 || >=8f91efd870ea5d8bc10b0fcc9740db51cd4c0c83 <310b5a537a78c358a4cd244bd767c1a517a05459 || >=8f91efd870ea5d8bc10b0fcc9740db51cd4c0c83 <806fcff98c1d7cb3c1dc0015e55ebdbe819e6b08 || >=8f91efd870ea5d8bc10b0fcc9740db51cd4c0c83 <8037c5b2b2a447df52542f4d8535895d837bdcbd || >=8f91efd870ea5d8bc10b0fcc9740db51cd4c0c83 <611e7821c4f83a671455658797336faecc3a5196 || >=8f91efd870ea5d8bc10b0fcc9740db51cd4c0c83 <5457025fa8ca3c0d2732109513de839e3e797190 || e1e5e263bbe0e6e9c3db36aa48a3c8acf546fa49 || 979965c33f734a1666af67900408f997ac669c23 || >=5.10.50 <5.10.266 || >=5.12.17 <5.13 || >=5.13.2 <5.144addb102154b7cf6e2310ccbe20c3c08619e520d, 894a9300d7fb2e2951da92e565ae6de7ddfb0a69, 1e5ca82eee59caca6988f9d6e859786aab8a5fa0, 310b5a537a78c358a4cd244bd767c1a517a05459, 806fcff98c1d7cb3c1dc0015e55ebdbe819e6b08, 8037c5b2b2a447df52542f4d8535895d837bdcbd, 611e7821c4f83a671455658797336faecc3a5196, 5457025fa8ca3c0d2732109513de839e3e797190, 5.10.266, 5.13, 5.14

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 1e5ca82eee59caca6988f9d6e859786aab8a5fa0; Linux/Linux to 4addb102154b7cf6e2310ccbe20c3c08619e520d if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Aug 22, 2026

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

    Aug 25, 2026

    Evidence: source:cvelist:source_dates:source-dates:record
  3. First seen by HOL

    Aug 22, 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
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
Upstream source description

In the Linux kernel, the following vulnerability has been resolved: sched/psi: Shut down rtpoll_timer in psi_cgroup_free() psi_schedule_rtpoll_work() is called locklessly from the scheduler hotpath and can race psi_trigger_destroy() taking down the last rtpoll trigger under rtpoll_trigger_lock: psi_schedule_rtpoll_work() psi_trigger_destroy() rcu_read_lock(); task = rcu_dereference(rtpoll_task); rcu_assign_pointer(rtpoll_task, NULL); timer_delete(&rtpoll_timer); mod_timer(&rtpoll_timer, ...); rcu_read_unlock(); synchronize_rcu(); kthread_stop(task_to_destroy); The group can then be freed with the re-armed timer still pending, and poll_timer_fn() runs on freed memory. 461daba06bdc ("psi: eliminate kthread_worker from psi trigger scheduling mechanism") deleted the timer synchronously after the synchronize_rcu(), which prevented this but raced trigger creation instead: the deletion could cancel the timer that a new trigger set armed during the grace period and, as creation also reinitialized the timer at the time, corrupt it. 8f91efd870ea ("psi: Fix race between psi_trigger_create/destroy") moved the initialization into group_init() and the deletion into the locked section, trading the creation races for the window above. Neither placement in the destruction path works. A pending timer firing while the group is alive is harmless though. poll_timer_fn() just wakes the rtpoll waitqueue and doesn't re-arm itself. Bind the timer to the group's lifetime instead and shut it down in psi_cgroup_free(). Nothing can arm it by then. timer_shutdown_sync() because the timer is never armed again.

Quoted source text, attributed separately from HOL analysis.

Related CVEs

  • Gitea OAuth2 refresh token grant accepts access tokensSame generic ecosystem
  • Langflow OSS is affected by multiple vulnerabilitiesSame generic ecosystem
  • Langflow OSS is affected by multiple vulnerabilitiesSame generic ecosystem
  • Langflow OSS is affected by multiple vulnerabilitiesSame generic ecosystem
  • Langflow OSS is affected by multiple vulnerabilitiesSame generic ecosystem
  • Langflow OSS is affected by multiple vulnerabilitiesSame generic ecosystem

Record context

Vulnerability class
Vulnerability
EPSS
Not reported
CWE IDs
Not reported
Source
CVE List V5
Source checked
Oct 7, 2026
References
8 linked sources
Open source record