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 81016 platformx86amdpmc propagate smu errors and
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
  • Contact
  • Blog
  • GitHub
  • Privacy
  • Terms of Service
Settings

Copyright © 2026 HOL DAO LLC. All rights reserved.

Back to active CVEs
High · CVSS 7.7CVE-2026-81016

platform/x86/amd/pmc: Propagate SMU errors and validate S2D addressCVE-2026-81016

Answer in brief

CVE-2026-81016 records a High severity (CVSS 7.7) vulnerability in platform/x86/amd/pmc: Propagate SMU errors and validate S2D address. 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 11, 2026Updated Oct 21, 2026Source checked Oct 27, 2026First seen by HOL Sep 11, 2026Material review Oct 21, 2026
Upstream Advisory

Key facts

Risk
High · CVSS 7.7
Exploitation
Not marked as known exploited
Affected software
4 mapped packages or products
Fix availability
Available

Why this deserves its current priority

CVSS is 7.7. 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>=3d7d407dfb05b257e15cb0c6b056428a4a8c2e5d <8178f59d76570b152d836bde07f5997f15861f04 || >=3d7d407dfb05b257e15cb0c6b056428a4a8c2e5d <775d4cde1f9737796ce7d8393521e9e8c5b49891 || >=3d7d407dfb05b257e15cb0c6b056428a4a8c2e5d <0225c1d637687b03726f00ac65b6def843d2c4648178f59d76570b152d836bde07f5997f15861f04, 775d4cde1f9737796ce7d8393521e9e8c5b49891, 0225c1d637687b03726f00ac65b6def843d2c464
Linux/Linuxgeneric>=3d7d407dfb05b257e15cb0c6b056428a4a8c2e5d <638e1ca5d4e2b4fdbb209db64926d013b34f3b79 || >=3d7d407dfb05b257e15cb0c6b056428a4a8c2e5d <8178f59d76570b152d836bde07f5997f15861f04 || >=3d7d407dfb05b257e15cb0c6b056428a4a8c2e5d <775d4cde1f9737796ce7d8393521e9e8c5b49891 || >=3d7d407dfb05b257e15cb0c6b056428a4a8c2e5d <0225c1d637687b03726f00ac65b6def843d2c464638e1ca5d4e2b4fdbb209db64926d013b34f3b79, 8178f59d76570b152d836bde07f5997f15861f04, 775d4cde1f9737796ce7d8393521e9e8c5b49891, 0225c1d637687b03726f00ac65b6def843d2c464
Linux/Linuxgeneric5.18Not reported
Linux/Linuxgeneric>=3d7d407dfb05b257e15cb0c6b056428a4a8c2e5d <85ef9d4c384c1d143c51580933674d94dba3b8d9 || >=3d7d407dfb05b257e15cb0c6b056428a4a8c2e5d <638e1ca5d4e2b4fdbb209db64926d013b34f3b79 || >=3d7d407dfb05b257e15cb0c6b056428a4a8c2e5d <8178f59d76570b152d836bde07f5997f15861f04 || >=3d7d407dfb05b257e15cb0c6b056428a4a8c2e5d <775d4cde1f9737796ce7d8393521e9e8c5b49891 || >=3d7d407dfb05b257e15cb0c6b056428a4a8c2e5d <0225c1d637687b03726f00ac65b6def843d2c46485ef9d4c384c1d143c51580933674d94dba3b8d9, 638e1ca5d4e2b4fdbb209db64926d013b34f3b79, 8178f59d76570b152d836bde07f5997f15861f04, 775d4cde1f9737796ce7d8393521e9e8c5b49891, 0225c1d637687b03726f00ac65b6def843d2c464

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 8178f59d76570b152d836bde07f5997f15861f04; Linux/Linux to 638e1ca5d4e2b4fdbb209db64926d013b34f3b79; Linux/Linux to 85ef9d4c384c1d143c51580933674d94dba3b8d9 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Sep 11, 2026

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

    Oct 21, 2026

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

    Sep 11, 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
Upstream source description

In the Linux kernel, the following vulnerability has been resolved: platform/x86/amd/pmc: Propagate SMU errors and validate S2D address amd_stb_s2d_init() discards the return value of several S2D SMU commands. When the SMU refuses a command (e.g. "SMU cmd failed. err: 0xff") the failure is only noticed indirectly - if at all - and reported as -EIO, masking the real error. More seriously, the S2D_PHYS_ADDR_LOW/HIGH return values are ignored, so on failure phys_addr_low/hi are left uninitialised and the assembled address is passed straight to devm_ioremap(). When the SMU leaves them at zero this maps physical address 0 and trips the ioremap-on-RAM warning: amd_pmc AMDI000B:00: SMU cmd failed. err: 0xff ioremap on RAM at 0x0000000000000000 - 0x0000000000ffffff WARNING: CPU: 13 PID: 4592 at arch/x86/mm/ioremap.c:... Check the return value of each SMU command and propagate it, and reject a zero physical address before calling devm_ioremap().

Quoted source text, attributed separately from HOL analysis.

Record context

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