medium
4.7
Advisory Published
CVE Published
Updated

CVE-2012-0045

First published: Wed 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, MSR_EFER 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: <a href="https://lkml.org/lkml/2011/12/28/170">https://lkml.org/lkml/2011/12/28/170</a> <a href="http://www.spinics.net/lists/kvm/msg66633.html">http://www.spinics.net/lists/kvm/msg66633.html</a> Proposed patch: <a href="http://www.spinics.net/lists/kvm/msg66633.html">http://www.spinics.net/lists/kvm/msg66633.html</a> Acknowledgements: Red Hat would like to thank Stephan Bärwolf for reporting this issue.

Credit: secalert@redhat.com

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

Remedy

https://github.com/torvalds/linux/commit/c2226fc9e87ba3da060e47333657cd6616652b84

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • 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.

  • 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.

  • 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.

  • 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.

  • 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.

Company

Resources

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.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203