All reports
Medium

kernel: KVM: s390: Zero initialize data structures for inject_pfault_token

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-89921

Probability of exploitation in the next 30 days: 0.22%

FIRST EPSS · 2026-11-19

Description

In the Linux kernel, the following vulnerability has been resolved: KVM: s390: Zero initialize data structures for inject_pfault_token __kvm_inject_pfault_token() only sets .type and .u.ext.ext_params2 of the on-stack struct kvm_s390_irq but the full ext substructure is copied into the cpu local variable on inject. ext_params and pad contain stale stack values. Interrupt delivery only uses ext_params2, so nothing leaks to the guest, but a host user can use the migration ioctls to get to the data. Fix by zero-initializing the irq struct. Do the same for the inti data structure.

A flaw was found in the Kernel-based Virtual Machine (KVM) for the s390 architecture in the Linux kernel. The __kvm_inject_pfault_token() function fails to fully zero-initialize certain data structures, specifically struct kvm_s390_irq. This oversight allows stale stack values to persist in the ext_params and pad fields. A local host user could exploit this by using migration input/output controls (ioctls) to access this uninitialized data, leading to information disclosure.