CVE-2026-89919
- Source
- https://cve.org/CVERecord?id=CVE-2026-89919
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-89919.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2026-89919
- Downstream
- Published
- 2026-09-16T10:32:14Z
- Modified
- 2026-09-18T03:48:33Z
- Severity
-
- 7.8 (High) CVSS_V3 - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H CVSS Calculator
- Summary
- KVM: s390: keyop: use mmu_lock to read gmap->asce
- Details
-
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.
- Database specific
{ "cna_assigner": "Linux", "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/89xxx/CVE-2026-89919.json" }- References
-
- https://git.kernel.org/stable/c/ae452b990e0544425f77045351c56e77158858e7
- https://git.kernel.org/stable/c/da07a751efa4583385f9f0f47113549fe8871242
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/89xxx/CVE-2026-89919.json
- https://nvd.nist.gov/vuln/detail/CVE-2026-89919
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git