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 80581 asoc sof ipc4 pcm continue the pipeline trigger
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
Unknown severity · Source severity not reportedCVE-2026-80581

ASoC: SOF: ipc4-pcm: Continue the pipeline trigger in case of IPC timeoutCVE-2026-80581

Answer in brief

CVE-2026-80581 records a Unknown severity vulnerability in ASoC: SOF: ipc4-pcm: Continue the pipeline trigger in case of IPC timeout. 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 26, 2026Updated Aug 27, 2026Source checked Oct 10, 2026First seen by HOL Aug 26, 2026Material review Aug 27, 2026
Upstream Advisory

Key facts

Risk
Unknown severitySource severity not reported
Exploitation
Not marked as known exploited
Affected software
3 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). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Linux/Linuxgeneric>=c40aad7c81e5fba34b70123ed7ce3397fa62a4d2 <f2435a46dfa1a5693cf2664afd022db66ee58121 || >=c40aad7c81e5fba34b70123ed7ce3397fa62a4d2 <6b512a5330ef1a41db7aff4b80c4e952b8d52f17 || >=c40aad7c81e5fba34b70123ed7ce3397fa62a4d2 <17661c67b206612cb3ba65d5ae726cd2015d0a53 || 3cac6eebea9b4bc5f041e157e45c76e212ad6759 || d153e8b154f9746ac969c85a4e6474760453647c || >=6.6.23 <6.7 || >=6.7.11 <6.8f2435a46dfa1a5693cf2664afd022db66ee58121, 6b512a5330ef1a41db7aff4b80c4e952b8d52f17, 17661c67b206612cb3ba65d5ae726cd2015d0a53, 6.7, 6.8
Linux/Linuxgeneric6.8Not reported
Linux/Linuxgeneric>=3cac6eebea9b4bc5f041e157e45c76e212ad6759 <4931c09d83877dc350106bae745321c3f295129b || >=c40aad7c81e5fba34b70123ed7ce3397fa62a4d2 <f2435a46dfa1a5693cf2664afd022db66ee58121 || >=c40aad7c81e5fba34b70123ed7ce3397fa62a4d2 <6b512a5330ef1a41db7aff4b80c4e952b8d52f17 || >=c40aad7c81e5fba34b70123ed7ce3397fa62a4d2 <17661c67b206612cb3ba65d5ae726cd2015d0a53 || d153e8b154f9746ac969c85a4e6474760453647c || >=6.6.23 <6.6.154 || >=6.7.11 <6.84931c09d83877dc350106bae745321c3f295129b, f2435a46dfa1a5693cf2664afd022db66ee58121, 6b512a5330ef1a41db7aff4b80c4e952b8d52f17, 17661c67b206612cb3ba65d5ae726cd2015d0a53, 6.6.154, 6.8

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 f2435a46dfa1a5693cf2664afd022db66ee58121; Linux/Linux to 4931c09d83877dc350106bae745321c3f295129b if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Aug 26, 2026

    Evidence: source:cvelist:source_dates:source-dates:record

  2. Source modified

    Aug 27, 2026

    Evidence: source:cvelist:source_dates:source-dates:record

  3. First seen by HOL

    Aug 26, 2026

Sources and claim methodology

  • 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: ASoC: SOF: ipc4-pcm: Continue the pipeline trigger in case of IPC timeout Ignore IPC errors for pipeline state change if the firmware state is crashed or the IPC has timed out. If the firmware has crashed the kernel still needs to go through the state changes to reset its internal to be able to correctly work the next time the DSP is booted up. The case with IPC timeout is a bit more problematic, but it has been rootcaused to be the result of system scheduling blockage and the firmware did actually received and handled the message, but the reply handling got blocked by issues outside of the SOF stack. So far the best way to handle this is to continue with setting the state.

Quoted source text, attributed separately from HOL analysis.

Related CVEs

  • WordPress ALD – Dropshipping and Fulfillment for AliExpress and WooCommerce plugin <= 2.2.4 - Broken Access Control vulnerabilitySame generic ecosystem
  • WordPress Pay With MetaMask For WooCommerce – Cryptocurrency Payment Gateway plugin <= 1.7.2 - Bypass Vulnerability vulnerabilitySame generic ecosystem
  • WordPress MicroPayments plugin <= 3.2.9 - Bypass Vulnerability vulnerabilitySame generic ecosystem
  • Helicone through v2025.08.21-1 SSRF via Jawn Webhook Sender DNS ResolutionSame generic ecosystem
  • slide-maker through 5.8.0 Path Traversal via generate_images_openai.pySame generic ecosystem
  • Tabularis through 0.27.0 Read-Only Bypass via MCP run_query SELECT ClassificationSame generic ecosystem

Record context

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