GPU VulnDB

Database/Kernel, userspace & hypervisor

KVM s390 zPCI: IRQ registration without a summary bit stored a bogus guest AISB address

CVSS 8.8CVE-2026-68454Kernel, userspace & hypervisorcurated

Impact

A guest registering adapter-interrupt forwarding without specifying a summary bit caused the GAITE to store virt_to_phys(page_address(NULL)) as the guest AISB location instead of zero, leaving the host's interrupt-forwarding table pointing at an address derived from a NULL page. The flaw is in the host hypervisor and is driven entirely by guest-supplied registration parameters, which is the kind of host-side state corruption a VM should not be able to cause. Scope is narrow for accelerator operators: this is IBM Z zPCI passthrough under KVM on s390, not x86 or Arm GPU hosts, so a conventional GPU datacenter is unaffected unless it runs s390 virtualization alongside.

Who can reach it

A guest running under KVM on s390 that can issue zPCI interrupt registration - local to the host, requires only normal guest privilege inside the VM. Not reachable on non-s390 hosts.

What to do

Take the stable kernel containing the fix (store 0 for the guest AISB when no summary bit is given) and reboot affected s390 KVM hosts after migrating or stopping guests. No runtime mitigation is described in the record.

References

Related entries

All Kernel, userspace & hypervisor entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.