CVE-2026-99500
Description
A flaw was found in the Linux kernel. A resource leak in the s390 PCI (Peripheral Component Interconnect) driver can result in a Denial of Service (DoS). When an error occurs while configuring interrupts during device hotplugging, an allocated tracking bit is never released. Over time, repeated device initialization failures can exhaust all available tracking bits, preventing new PCI devices from being added to the system until it is rebooted.
Statement
This vulnerability is rated as having a Low impact because triggering the leak requires repeated PCI device attachment failures under extreme conditions such as memory exhaustion on IBM Z (s390x) platforms. Only deployments running on the s390x architecture with hotplugged PCI adapters are exposed to this issue. Furthermore, exhaustion of the internal tracking bits does not crash the operating system or compromise data confidentiality and integrity; it only limits the ability to dynamically attach subsequent PCI hardware until the next system restart.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 1.9 | N/A | N/A |
| Attack Vector | Local | N/A | N/A |
| Attack Complexity | High | N/A | N/A |
| Privileges Required | High | N/A | N/A |
| User Interaction | None | N/A | N/A |
| Scope | Unchanged | N/A | N/A |
| Confidentiality | None | N/A | N/A |
| Integrity Impact | None | N/A | N/A |
| Availability Impact | Low | N/A | N/A |
Vector
Red Hat: CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:L
Understanding the Weakness (CWE)
Availability
Technical Impact: DoS: Resource Consumption (Other); DoS: Resource Consumption (Memory); DoS: Resource Consumption (CPU)
An attacker that can influence the allocation of resources that are not properly released could deplete the available resource pool and prevent all other processes from accessing the same type of resource. Frequently-affected resources include memory, CPU, disk space, power or battery, etc.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.