Bug 665470 (CVE-2010-4525) - CVE-2010-4525 kvm: x86: zero kvm_vcpu_events->interrupt.pad infoleak
Summary: CVE-2010-4525 kvm: x86: zero kvm_vcpu_events->interrupt.pad infoleak
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2010-4525
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 665407 665409 665471
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-12-23 23:32 UTC by Eugene Teo (Security Response)
Modified: 2023-05-11 16:06 UTC (History)
17 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-07-29 13:32:59 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2011:0007 0 normal SHIPPED_LIVE Important: kernel security and bug fix update 2011-01-11 19:44:55 UTC
Red Hat Product Errata RHSA-2011:0028 0 normal SHIPPED_LIVE Low: kvm security and bug fix update 2011-01-13 11:03:39 UTC

Description Eugene Teo (Security Response) 2010-12-23 23:32:13 UTC
kvm_vcpu_events.interrupt.pad field must be initialized before being copied to
userspace, otherwise kernel memory is leaked.

Acknowledgements:

Red Hat would like to thank Stephan Mueller of atsec information security for reporting this issue.

Comment 3 errata-xmlrpc 2011-01-11 19:45:57 UTC
This issue has been addressed in following products:

  Red Hat Enterprise Linux 6

Via RHSA-2011:0007 https://rhn.redhat.com/errata/RHSA-2011-0007.html

Comment 4 errata-xmlrpc 2011-01-13 23:38:51 UTC
This issue has been addressed in following products:

  Red Hat Enterprise Linux 5

Via RHSA-2011:0028 https://rhn.redhat.com/errata/RHSA-2011-0028.html

Comment 5 errata-xmlrpc 2011-01-14 09:04:05 UTC
This issue has been addressed in following products:

  Red Hat Enterprise Linux 5

Via RHSA-2011:0028 https://rhn.redhat.com/errata/RHSA-2011-0028.html


Note You need to log in before you can comment on or make changes to this bug.