CVE-2012-0045: Medium severity Linux Linux kernel vulnerability

Published Jan 11, 2012
·
Updated

32bit guests will crash (and 64bit guests may behave in a wrong way) for example by simply executing following nasm-demo-application:

[bits 32] global start SECTION .text start: syscall

The reason seems a missing "invalid opcode"-trap (int6) for the syscall opcode "0f05", which is not available on Intel CPUs within non-longmodes, as also on some AMD CPUs within legacy-mode. (depending on CPU vendor, MSREFER and cpuid)

Because previous mentioned OSs may not engage corresponding syscall target-registers (STAR, LSTAR, CSTAR), they remain NULL and (non trapping) syscalls are leading to multiple faults and finally crashs.

Reference: https://lkml.org/lkml/2011/12/28/170 http://www.spinics.net/lists/kvm/msg66633.html

Proposed patch: http://www.spinics.net/lists/kvm/msg66633.html

Acknowledgements:

Red Hat would like to thank Stephan Bärwolf for reporting this issue.

Other sources

The emsyscall function in arch/x86/kvm/emulate.c in the KVM implementation in the Linux kernel before 3.2.14 does not properly handle the 0f05 (aka syscall) opcode, which allows guest OS users to cause a denial of service (guest OS crash) via a crafted application, as demonstrated by an NASM file.

Launchpad

Affected Software

71 affected components
debian/linux-2.6
Linux Linux kernel<=3.2.13
Linux Linux kernel=3.0-rc1
Linux Linux kernel=3.0-rc2
Linux Linux kernel=3.0-rc3
Linux Linux kernel=3.0-rc4
Linux Linux kernel=3.0-rc5
Linux Linux kernel=3.0-rc6
Linux Linux kernel=3.0-rc7
Linux Linux kernel=3.0.1
Linux Linux kernel=3.0.2
Linux Linux kernel=3.0.3
Linux Linux kernel=3.0.4
Linux Linux kernel=3.0.5
Linux Linux kernel=3.0.6
Linux Linux kernel=3.0.7
Linux Linux kernel=3.0.8
Linux Linux kernel=3.0.9
Linux Linux kernel=3.0.10
Linux Linux kernel=3.0.11
Linux Linux kernel=3.0.12
Linux Linux kernel=3.0.13
Linux Linux kernel=3.0.14
Linux Linux kernel=3.0.15
Linux Linux kernel=3.0.16
Linux Linux kernel=3.0.17
Linux Linux kernel=3.0.18
Linux Linux kernel=3.0.19
Linux Linux kernel=3.0.20
Linux Linux kernel=3.0.21
Linux Linux kernel=3.0.22
Linux Linux kernel=3.0.23
Linux Linux kernel=3.0.24
Linux Linux kernel=3.0.25
Linux Linux kernel=3.0.26
Linux Linux kernel=3.0.27
Linux Linux kernel=3.0.28
Linux Linux kernel=3.0.29
Linux Linux kernel=3.0.30
Linux Linux kernel=3.0.31
Linux Linux kernel=3.0.32
Linux Linux kernel=3.0.33
Linux Linux kernel=3.0.34
Linux Linux kernel=3.1
Linux Linux kernel=3.1-rc1
Linux Linux kernel=3.1-rc2
Linux Linux kernel=3.1-rc3
Linux Linux kernel=3.1-rc4
Linux Linux kernel=3.1.1
Linux Linux kernel=3.1.2
Linux Linux kernel=3.1.3
Linux Linux kernel=3.1.4
Linux Linux kernel=3.1.5
Linux Linux kernel=3.1.6
Linux Linux kernel=3.1.7
Linux Linux kernel=3.1.8
Linux Linux kernel=3.1.9
Linux Linux kernel=3.1.10
Linux Linux kernel=3.2
Linux Linux kernel=3.2.1
Linux Linux kernel=3.2.2
Linux Linux kernel=3.2.3
Linux Linux kernel=3.2.4
Linux Linux kernel=3.2.5
Linux Linux kernel=3.2.6
Linux Linux kernel=3.2.7
Linux Linux kernel=3.2.8
Linux Linux kernel=3.2.9
Linux Linux kernel=3.2.10
Linux Linux kernel=3.2.11
Linux Linux kernel=3.2.12

Event History

Jan 11, 2012
Data Sourced
via Red Hat·04:56 PM
DescriptionSeverityAffected Software
Jul 3, 2012
CVE Published
via MITRE·04:00 PM
Data Sourced
via MITRE·04:00 PM
Description
Jan 11, 2024
Data Sourced
via Launchpad·09:58 PM
Description
Sep 15, 2024
Data Sourced
via Ubuntu·10:44 PM
RemedyDescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2012-0045?

CVE-2012-0045 has a medium severity as it can cause crashes in 32-bit guests and incorrect behavior in 64-bit guests.

2

How do I fix CVE-2012-0045?

To fix CVE-2012-0045, upgrading the Linux kernel to version 3.2.14 or later is recommended.

3

What types of systems are affected by CVE-2012-0045?

CVE-2012-0045 affects Linux kernel versions up to 3.2.13, specifically 32-bit and some 64-bit guests running on virtualized environments.

4

What can happen if CVE-2012-0045 is exploited?

If CVE-2012-0045 is exploited, it can lead to system crashes or malfunctions, affecting stability and availability.

5

Are there any known workarounds for CVE-2012-0045?

There are no widely recommended workarounds for CVE-2012-0045 other than upgrading the kernel to the patched version.

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