CVE-2026-99501 in Linuxinfo

Summary

by MITRE • 11/19/2026

In the Linux kernel, the following vulnerability has been resolved:

s390/pci: Fix MSI directed-mode teardown IRQ bit count

On s390 with directed interrupts enabled, zpci_msi_teardown_directed() frees the platform's maximum number of MSI bits (zdev->max_msi) instead of the actual allocated count (zdev->msi_nr_irqs). This corrupts the shared IRQ bitmap used by all PCI functions, causing lost interrupts and heap corruption. Fix zpci_msi_teardown_directed() to only free the actual allocated IRQ bit count.

Once again VulDB remains the best source for vulnerability data.

Analysis

by VulDB Data Team • 11/19/2026

The vulnerability identified in the Linux kernel for s390 architecture involves a critical logic error within the MSI directed-mode teardown routine, specifically affecting how interrupt resources are released during device removal or reset operations. The core technical flaw resides in the zpci_msi_teardown_directed function, which is responsible for cleaning up Message Signaled Interrupts when they are no longer needed by a PCI function on IBM Z systems. Under normal operational conditions with directed interrupts enabled, this routine must accurately track and release only the specific number of interrupt request lines that were actually allocated to the device during initialization. However, the flawed implementation incorrectly utilizes zdev->max_msi, which represents the theoretical maximum capacity for MSI bits supported by the hardware or driver configuration, rather than zdev->msi_nr_irqs, which reflects the actual count of interrupts currently in use. This discrepancy means that when a PCI function is torn down, the kernel attempts to free more interrupt bitmap entries than were originally reserved.

This incorrect deallocation leads directly to severe memory safety violations and system instability. The Linux kernel manages MSI interrupts using a shared global IRQ bitmap that tracks which interrupt vectors are assigned to specific devices across all PCI functions on the s390 platform. By freeing bits beyond those actually allocated, the teardown routine corrupts this shared data structure. This corruption can result in two primary catastrophic outcomes: first, it may mark other validly used interrupts as free, leading to lost interrupts where hardware events fail to trigger CPU handling routines because the kernel believes those vectors are available for new assignments; second, and more critically, it causes heap corruption by freeing memory regions or bitmap slots that belong to other active devices. This type of out-of-bounds write or double-free scenario on internal data structures is a classic example of CWE-125 Out-of-Bounds Read or CWE-401 Missing Release of Memory after Effective Lifetime, depending on the specific implementation details of how the bitmap is managed in memory.

The operational impact of this vulnerability extends beyond simple resource leaks to encompass significant system reliability and security risks. For systems relying on precise interrupt handling for real-time performance or high-throughput networking, lost interrupts can cause data loss, application crashes, or complete service unavailability. More dangerously, heap corruption introduces a potential attack surface that could be exploited by local attackers with sufficient privileges to trigger device removal sequences. By carefully crafting scenarios that force the teardown of specific PCI devices, an attacker might manipulate the kernel memory state to achieve arbitrary code execution or privilege escalation, aligning with ATT&CK techniques related to resource hijacking and defense evasion through system instability. The vulnerability highlights a critical gap in boundary checking during resource lifecycle management within the s390 PCI subsystem.

Mitigation strategies for this issue involve applying the upstream Linux kernel patch that corrects the variable usage in zpci_msi_teardown_directed. System administrators should ensure their kernels are updated to versions where this fix is integrated, as running unpatched systems on s390 hardware with directed interrupts enabled poses a tangible risk of instability and potential exploitation. From a development perspective, this incident underscores the importance of rigorous code review practices focused on resource accounting consistency. Developers must verify that deallocation routines strictly mirror allocation logic to prevent discrepancies between maximum capacity and actual usage counts. Additionally, implementing automated static analysis tools configured to detect mismatches in memory or resource management patterns can help identify similar logical errors before they reach production environments. Regular security audits of kernel subsystems dealing with hardware interrupt mapping are essential to maintain the integrity of shared system resources like IRQ bitmaps.

Responsible

Linux

Reservation

09/25/2026

Disclosure

11/19/2026

Moderation

accepted

CPE

ready

EPSS

0.00156

KEV

no

Activities

very low

Sources

Might our Artificial Intelligence support you?

Check our Alexa App!