KVM: s390: keyop: use mmu_lock to read gmap->asce
- 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 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: keyop: use mmu_lock to read gmap->asce Every other dat_* consumer in this file (kvm_s390_get_skeys, set_skeys, get_cmma_bits, set_cmma_bits, MEM_CLR_CMMA, kvm_s390_fixup_prefix, kvm_test_age_gfn, kvm_age_gfn) reads kvm->arch.gmap->asce inside the mmu_lock read-side. keyop is the only outlier. gmap->asce is mutated under write_lock(mmu_lock) by gmap_set_limit() and keyop might use a stale asce value for walking as KVM_S390_KEYOP and KVM_S390_VM_MEM_LIMIT_SIZE can run concurrently. This can result in memory corruption.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 0ee4ddc1647b8b3b9e7a94d798a1774a764428c1 · fixed in ae452b990e0544425f77045351c56e77158858e7; From 0ee4ddc1647b8b3b9e7a94d798a1774a764428c1 · fixed in da07a751efa4583385f9f0f47113549fe8871242
- Linux Linux
7.0
- KernelLinux
From 7.0.0 · fixed in 7.2.5