kvm: s390: Reject memory region operations for ucontrol VMs
- 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.10.3
- 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
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
In the Linux kernel, the following vulnerability has been resolved: kvm: s390: Reject memory region operations for ucontrol VMs This change rejects the KVM_SET_USER_MEMORY_REGION and KVM_SET_USER_MEMORY_REGION2 ioctls when called on a ucontrol VM. This is necessary since ucontrol VMs have kvm->arch.gmap set to 0 and would thus result in a null pointer dereference further in. Memory management needs to be performed in userspace and using the ioctls KVM_S390_UCAS_MAP and KVM_S390_UCAS_UNMAP. Also improve s390 specific documentation for KVM_SET_USER_MEMORY_REGION and KVM_SET_USER_MEMORY_REGION2. [frankja@linux.ibm.com: commit message spelling fix, subject prefix fix]
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From 27e0393f15fc8bc855c6a888387ff5ffd2181089 · fixed in 705a8b8cc5a44b206096abb1bfdc8bc43b3c75c7; From 27e0393f15fc8bc855c6a888387ff5ffd2181089 · fixed in 49c9945c054df4c22008e2bf87ca74d3e2507aa6; From 27e0393f15fc8bc855c6a888387ff5ffd2181089 · fixed in 7816e58967d0e6cadce05c8540b47ed027dc2499
- Linux Linux
3.4
- KernelLinux
From 3.4.0 · fixed in 6.6.160; From 6.7.0 · fixed in 6.10.3