First published: Thu Nov 04 2010(Updated: )
Description of problem: Structures kvm_vcpu_events, kvm_debugregs, kvm_pit_state2 and kvm_clock_data are copied to userland with some padding and reserved fields unitialized. It leads to leaking of contents of kernel stack memory. Reference: <a href="http://www.spinics.net/lists/kvm/msg44130.html">http://www.spinics.net/lists/kvm/msg44130.html</a> <a href="http://git.kernel.org/?p=virt/kvm/kvm.git;a=commit;h=831d9d02f9522e739825a51a11e3bc5aa531a905">http://git.kernel.org/?p=virt/kvm/kvm.git;a=commit;h=831d9d02f9522e739825a51a11e3bc5aa531a905</a> Acknowledgements: Red Hat would like to thank Vasiliy Kulikov of Openwall for reporting this issue.
Affected Software | Affected Version | How to fix |
---|---|---|
Red Hat QEMU-KVM |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-649920 is considered high due to potential kernel memory leakage.
To fix REDHAT-BUG-649920, apply the latest patches and updates provided by Red Hat for KVM.
REDHAT-BUG-649920 affects Red Hat KVM as the primary software that is impacted.
REDHAT-BUG-649920 is a vulnerability that allows for the leakage of kernel stack memory contents.
Yes, there is a risk of exploitation associated with REDHAT-BUG-649920, as it allows unauthorized access to sensitive kernel memory.