CVE-2012-2121: Medium severity linux kernel vulnerability

Published Apr 19, 2012
·
Updated

KVM uses memory slots to track and map guest regions of memory. When device assignment is used, the pages backing these slots are pinned in memory using getuserpages and mapped into the iommu. The problem is that when a memory slot is destroyed the pages for the associated memory slot are neither unpinned nor unmapped from the iommu.

The problem is that those pages are now never unpinned and continue to have an increased reference count. This is therefore a potential page leak from the kvm kernel module.

On Red Hat Enterprise Linux, local user with ability to assign device (with access to PCI sysfs files for a device) could use this flaw to DoS the system.

With upstream qemu-kvm/kvm privileged guest user that could hotunplug and then hotplug back certain devices could potentially use this flaw to DoS the host.

Upstream fixes: http://git.kernel.org/?p=virt/kvm/kvm.git;a=commit;h=32f6daad4651a748a58a3ab6da0611862175722f http://git.kernel.org/?p=virt/kvm/kvm.git;a=commit;h=21a1416a1c945c5aeaeaf791b63c64926018eb77

References: https://lkml.org/lkml/2012/4/11/248

Other sources

The KVM implementation in the Linux kernel before 3.3.4 does not properly manage the relationships between memory slots and the iommu, which allows guest OS users to cause a denial of service (memory leak and host OS crash) by leveraging administrative access to the guest OS to conduct hotunplug and hotplug operations on devices.

Launchpad

Affected Software

2 affected components
debian/linux-2.6
Linux Linux kernel<=3.3.3

Event History

Apr 19, 2012
Data Sourced
via Red Hat·10:10 AM
DescriptionSeverityAffected Software
May 17, 2012
CVE Published
via MITRE·10:00 AM
Data Sourced
via MITRE·10:00 AM
Description
Data Sourced
via NVD·11:00 AM
DescriptionSeverityWeaknessAffected Software
Jan 11, 2024
Data Sourced
via Launchpad·09:58 PM
Description
Sep 20, 2024
Data Sourced
via Ubuntu·12:49 AM
RemedyDescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2012-2121?

CVE-2012-2121 has a medium to high severity rating due to potential memory corruption that could be exploited.

2

What software is affected by CVE-2012-2121?

CVE-2012-2121 affects various versions of the Linux Kernel up to 3.3.3 and the linux-2.6 package on Debian.

3

How do I fix CVE-2012-2121?

To fix CVE-2012-2121, update your Linux Kernel to a version that has patched this vulnerability.

4

What are the implications of CVE-2012-2121?

Exploitation of CVE-2012-2121 may allow attackers to perform unauthorized actions through memory corruption.

5

Is CVE-2012-2121 related to virtualization?

Yes, CVE-2012-2121 is related to the KVM (Kernel-based Virtual Machine) and impacts guest memory management.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203