CVE-2026-80891

KVM: s390: pci: Validate AIBV and AISB before pinning guest pages

N/A
Published: September 4, 2026 at 05:11 PM UTC
Updated: September 4, 2026 at 06:36 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: KVM: s390: pci: Validate AIBV and AISB before pinning guest pages The AIBV holds one bit per MSI-X vector for a given function. The size of the bit vector is derived from the NOI and the AIBVO. If the size of the AIBV exceeds a single page boundary, then reject the request as we cannot safely pin the guest AIBV. Similarly reject the request if the AISB address is not 8-byte aligned as the architecture requires doubleword alignment for the summary bit address. Since the AISBO can address up to 64 bits, the size of the AISB can only be 8 bytes for the function. This also ensures the AISB doesn't exceed a single page boundary.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

6.0 ≤ v < 6.1.1836.0 ≤ v < 6.12.1036.0 ≤ v < 6.18.446.0 ≤ v < 6.6.1516.0 ≤ v < 7.1.86.0 ≤ v < 7.23c5a1b6f0a18520a0edd0600fef6f1a8553b8fdc6.0
Vendor states this is fixed in 15df7700dd99f8a37f5c6ed2dcf1e33009cdba47 (fixed)
Vendor states this is fixed in 3a1c64220ede4ac9ef9a3e76f008ff60a34f4c48 (fixed)
Vendor states this is fixed in 868d32ac72cba21c5c6d8a66a814b7c25a3a5c01 (fixed)
Vendor states this is fixed in b878ba7e28144c9a857bc847d31f3c45413450ac (fixed)
Vendor states this is fixed in f00ef8efd41440129ccd88f4a1ebebf8d61d297f (fixed)
Vendor states this is fixed in fbfe683f8b1ae7e40b56bdd6daf5bd671bc3a528 (fixed)
Vendor states this is fixed in 6.0 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.103 (unaffected)
Vendor states this is fixed in 6.18.44 (unaffected)
Vendor states this is fixed in 6.6.151 (unaffected)
Vendor states this is fixed in 7.1.8 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card