USN-1689-1: Linux kernel vulnerabilities

Published Jan 15, 2013
·
Updated

Jon Howell reported a flaw in the Linux kernel's KVM (Kernel-based virtual machine) subsystem's handling of the XSAVE feature. On hosts, using qemu userspace, without the XSAVE feature an unprivileged local attacker could exploit this flaw to crash the system. (CVE-2012-4461) A flaw was discovered in the Linux kernel's handling of script execution when module loading is enabled. A local attacker could exploit this flaw to cause a leak of kernel stack contents. (CVE-2012-4530)

Affected Software

16 affected componentsFixes available
All of the following
ubuntu/linux-image-3.0.0-30-server<3.0.0-30.47
3.0.0-30.47
Ubuntu Ubuntu=11.10
All of the following
ubuntu/linux-image-3.0.0-30-powerpc-smp<3.0.0-30.47
3.0.0-30.47
Ubuntu Ubuntu=11.10
All of the following
ubuntu/linux-image-3.0.0-30-virtual<3.0.0-30.47
3.0.0-30.47
Ubuntu Ubuntu=11.10
All of the following
ubuntu/linux-image-3.0.0-30-powerpc64-smp<3.0.0-30.47
3.0.0-30.47
Ubuntu Ubuntu=11.10
All of the following
ubuntu/linux-image-3.0.0-30-powerpc<3.0.0-30.47
3.0.0-30.47
Ubuntu Ubuntu=11.10
All of the following
ubuntu/linux-image-3.0.0-30-generic-pae<3.0.0-30.47
3.0.0-30.47
Ubuntu Ubuntu=11.10
All of the following
ubuntu/linux-image-3.0.0-30-omap<3.0.0-30.47
3.0.0-30.47
Ubuntu Ubuntu=11.10
All of the following
ubuntu/linux-image-3.0.0-30-generic<3.0.0-30.47
3.0.0-30.47
Ubuntu Ubuntu=11.10

Event History

Jan 15, 2013
Advisory Published
via Ubuntu·12:00 AM

Child vulnerabilities

Contains the following vulnerabilities.

Frequently Asked Questions

1

What is the severity of USN-1689-1?

The severity of USN-1689-1 is critical due to the potential for local unprivileged attackers to crash the system.

2

How do I fix USN-1689-1?

To fix USN-1689-1, you should update to the kernel version 3.0.0-30.47 or later.

3

What systems are affected by USN-1689-1?

USN-1689-1 affects Ubuntu 11.10 running the kernel versions prior to 3.0.0-30.47.

4

What kind of attack can exploit USN-1689-1?

USN-1689-1 can be exploited by an unprivileged local attacker to crash the system.

5

Is there a workaround for USN-1689-1?

There is no recommended workaround for USN-1689-1; updating the kernel is the only safe resolution.

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