CVE-2026-89921
KVM: s390: Zero initialize data structures for inject_pfault_token
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.6.160, 6.12.112, 6.18.52, 7.2.5
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
3.19
- KernelLinux
From 3.19.0 · fixed in 6.6.160; From 6.7.0 · fixed in 6.12.112; From 6.13.0 · fixed in 6.18.52; From 6.19.0 · fixed in 7.2.5
References 8
git.kernel.org
- stable/c/3da26db3323cbccf509005fdbc4ebae842d323cd
- stable/c/5b0ae4443383fbacd905522f0c95ad6c85a3b43e
- stable/c/7090818ba774d254eba80979c2d4da23d91de02f
- stable/c/ab1a8a3c9971200938093370da4c67d4427c25f2
- stable/c/b8abc760fa18a389319d977834a30550b3ec18e8
- stable/c/9b046de62b8098af6e2ba820b125ec9dc5f162c8
- stable/c/134f235e0e8de54611a72d3cc3f63e5f31246baa
- stable/c/4e2c7f7cbc27418f9a290399b986c1b85ff93b90