Описание
Linux kernel 2.6.33 and 2.6.34.y does not initialize the kvm_vcpu_events->interrupt.pad structure member, which allows local users to obtain potentially sensitive information from kernel stack memory via unspecified vectors.
Linux kernel 2.6.33 and 2.6.34.y does not initialize the kvm_vcpu_events->interrupt.pad structure member, which allows local users to obtain potentially sensitive information from kernel stack memory via unspecified vectors.
Ссылки
- https://nvd.nist.gov/vuln/detail/CVE-2010-4525
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2010-4525
- https://exchange.xforce.ibmcloud.com/vulnerabilities/64519
- http://osvdb.org/70377
- http://secunia.com/advisories/42890
- http://www.openwall.com/lists/oss-security/2011/01/05/1
- http://www.openwall.com/lists/oss-security/2011/01/05/9
- http://www.openwall.com/lists/oss-security/2011/01/06/3
- http://www.redhat.com/support/errata/RHSA-2011-0007.html
- http://www.redhat.com/support/errata/RHSA-2011-0028.html
- http://www.securityfocus.com/bid/45676
- http://www.vupen.com/english/advisories/2011/0123
Связанные уязвимости
Linux kernel 2.6.33 and 2.6.34.y does not initialize the kvm_vcpu_events->interrupt.pad structure member, which allows local users to obtain potentially sensitive information from kernel stack memory via unspecified vectors.
Linux kernel 2.6.33 and 2.6.34.y does not initialize the kvm_vcpu_events->interrupt.pad structure member, which allows local users to obtain potentially sensitive information from kernel stack memory via unspecified vectors.
Linux kernel 2.6.33 and 2.6.34.y does not initialize the kvm_vcpu_events->interrupt.pad structure member, which allows local users to obtain potentially sensitive information from kernel stack memory via unspecified vectors.
Linux kernel 2.6.33 and 2.6.34.y does not initialize the kvm_vcpu_even ...
