KVM: s390: keyop: use mmu_lock to read gmap->asce
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel ae452b990e0544425f77045351c56e77158858e7 and Kernel da07a751efa4583385f9f0f47113549fe8871242.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =7.0, >=0ee4ddc1647b8b3b9e7a94d798a1774a764428c1 <ae452b990e0544425f77045351c56e77158858e7, >=0ee4ddc1647b8b3b9e7a94d798a1774a764428c1 <da07a751efa4583385f9f0f47113549fe8871242 | ae452b990e0544425f77045351c56e77158858e7, da07a751efa4583385f9f0f47113549fe8871242 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket