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 89795 pci allow per function pci slots to fix slot
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 8.4CVE-2026-89795

PCI: Allow per function PCI slots to fix slot reset on s390CVE-2026-89795

Answer in brief

CVE-2026-89795 records a High severity (CVSS 8.4) vulnerability in PCI: Allow per function PCI slots to fix slot reset on s390. 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 16, 2026Updated Oct 30, 2026Source checked Oct 31, 2026First seen by HOL Sep 16, 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
Oct 31, 2026
References
6 linked sources
Open source record

Key facts

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

Why this deserves its current priority

CVSS is 8.4. 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>=44510d6fa0c00aa90b80075caa6b313b25927475 <0d1a7d67f45645106578d65181e4e492dd20ed79 || >=44510d6fa0c00aa90b80075caa6b313b25927475 <2050d900f9adbd6d6f38d30e182bcd9ad3108467 || >=44510d6fa0c00aa90b80075caa6b313b25927475 <ecdcceed4d377b02d4ea036b65f83f962c38ede7 || >=44510d6fa0c00aa90b80075caa6b313b25927475 <dcc5bec09e23bbc4f9de055a11fce9937244f2c80d1a7d67f45645106578d65181e4e492dd20ed79, 2050d900f9adbd6d6f38d30e182bcd9ad3108467, ecdcceed4d377b02d4ea036b65f83f962c38ede7, dcc5bec09e23bbc4f9de055a11fce9937244f2c8
Linux/Linuxgeneric5.8Not reported
Linux/Linuxgeneric>=44510d6fa0c00aa90b80075caa6b313b25927475 <2050d900f9adbd6d6f38d30e182bcd9ad3108467 || >=44510d6fa0c00aa90b80075caa6b313b25927475 <ecdcceed4d377b02d4ea036b65f83f962c38ede7 || >=44510d6fa0c00aa90b80075caa6b313b25927475 <dcc5bec09e23bbc4f9de055a11fce9937244f2c82050d900f9adbd6d6f38d30e182bcd9ad3108467, ecdcceed4d377b02d4ea036b65f83f962c38ede7, dcc5bec09e23bbc4f9de055a11fce9937244f2c8
Linux/Linuxgeneric>=44510d6fa0c00aa90b80075caa6b313b25927475 <b4a80e9e639cf09ef5c66b7f262c9cb5ab37bdde || >=44510d6fa0c00aa90b80075caa6b313b25927475 <0d1a7d67f45645106578d65181e4e492dd20ed79 || >=44510d6fa0c00aa90b80075caa6b313b25927475 <2050d900f9adbd6d6f38d30e182bcd9ad3108467 || >=44510d6fa0c00aa90b80075caa6b313b25927475 <ecdcceed4d377b02d4ea036b65f83f962c38ede7 || >=44510d6fa0c00aa90b80075caa6b313b25927475 <dcc5bec09e23bbc4f9de055a11fce9937244f2c8b4a80e9e639cf09ef5c66b7f262c9cb5ab37bdde, 0d1a7d67f45645106578d65181e4e492dd20ed79, 2050d900f9adbd6d6f38d30e182bcd9ad3108467, ecdcceed4d377b02d4ea036b65f83f962c38ede7, dcc5bec09e23bbc4f9de055a11fce9937244f2c8
Linux/Linuxgeneric>=44510d6fa0c00aa90b80075caa6b313b25927475 <afdd497ca3836eda13530ab75b416d52f6d6129a || >=44510d6fa0c00aa90b80075caa6b313b25927475 <b4a80e9e639cf09ef5c66b7f262c9cb5ab37bdde || >=44510d6fa0c00aa90b80075caa6b313b25927475 <0d1a7d67f45645106578d65181e4e492dd20ed79 || >=44510d6fa0c00aa90b80075caa6b313b25927475 <2050d900f9adbd6d6f38d30e182bcd9ad3108467 || >=44510d6fa0c00aa90b80075caa6b313b25927475 <ecdcceed4d377b02d4ea036b65f83f962c38ede7 || >=44510d6fa0c00aa90b80075caa6b313b25927475 <dcc5bec09e23bbc4f9de055a11fce9937244f2c8afdd497ca3836eda13530ab75b416d52f6d6129a, b4a80e9e639cf09ef5c66b7f262c9cb5ab37bdde, 0d1a7d67f45645106578d65181e4e492dd20ed79, 2050d900f9adbd6d6f38d30e182bcd9ad3108467, ecdcceed4d377b02d4ea036b65f83f962c38ede7, dcc5bec09e23bbc4f9de055a11fce9937244f2c8

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 0d1a7d67f45645106578d65181e4e492dd20ed79; Linux/Linux to 2050d900f9adbd6d6f38d30e182bcd9ad3108467; Linux/Linux to b4a80e9e639cf09ef5c66b7f262c9cb5ab37bdde; Linux/Linux to afdd497ca3836eda13530ab75b416d52f6d6129a if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Sep 16, 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 16, 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: PCI: Allow per function PCI slots to fix slot reset on s390 On s390 systems, which use a machine level hypervisor, PCI devices are always accessed through a form of PCI pass-through which fundamentally operates on a per PCI function granularity. This is also reflected in the s390 PCI hotplug driver which creates hotplug slots for individual PCI functions. Its reset_slot() function, which is a wrapper for zpci_hot_reset_device(), thus also resets individual functions. Currently, the pci_create_slot() assigns the same pci_slot object to multifunction devices. This approach worked fine on s390 systems that only exposed virtual functions as individual PCI domains to the operating system. Since commit 44510d6fa0c0 ("s390/pci: Handling multifunctions") s390 supports exposing the topology of multifunction PCI devices by grouping them in a shared PCI domain. This creates a problem when resetting a function through the hotplug driver's slot_reset() interface. When attempting to reset a function through the hotplug driver, the shared slot assignment causes the wrong function to be reset instead of the intended one. It also leaks memory as we do create a pci_slot object for the function, but don't correctly free it in pci_slot_release(). Add a flag for struct pci_slot to allow per function PCI slots for functions managed through a hypervisor, which exposes individual PCI functions while retaining the topology. Since we can use all 8 bits for slot 'number' (for ARI devices), change slot 'number' u16 to account for special values PCI_SLOT_PLACEHOLDER and PCI_SLOT_ALL_DEVICES.

Quoted source text, attributed separately from HOL analysis.