USN-1390-1: Linux kernel vulnerabilities

Published Mar 6, 2012
·
Updated

Dan Rosenberg reported errors in the OSS (Open Sound System) MIDI interface. A local attacker on non-x86 systems might be able to cause a denial of service. (CVE-2011-1476) Dan Rosenberg reported errors in the kernel's OSS (Open Sound System) driver for Yamaha FM synthesizer chips. A local user can exploit this to cause memory corruption, causing a denial of service or privilege escalation. (CVE-2011-1477) Ben Hutchings reported a flaw in the kernel's handling of corrupt LDM partitions. A local user could exploit this to cause a denial of service or escalate privileges. (CVE-2011-2182) A flaw was discovered in the Linux kernel's NFSv4 (Network File System version 4) file system. A local, unprivileged user could use this flaw to cause a denial of service by creating a file in a NFSv4 filesystem. (CVE-2011-4324) A flaw was found in how the linux kernel handles user-space held futexs. An unprivileged user could exploit this flaw to cause a denial of service or possibly elevate privileges. (CVE-2012-0028)

Affected Software

36 affected componentsFixes available
All of the following
ubuntu/linux-image-2.6.24-31-powerpc<2.6.24-31.99
2.6.24-31.99
Ubuntu Ubuntu=8.04
All of the following
ubuntu/linux-image-2.6.24-31-sparc64<2.6.24-31.99
2.6.24-31.99
Ubuntu Ubuntu=8.04
All of the following
ubuntu/linux-image-2.6.24-31-virtual<2.6.24-31.99
2.6.24-31.99
Ubuntu Ubuntu=8.04
All of the following
ubuntu/linux-image-2.6.24-31-server<2.6.24-31.99
2.6.24-31.99
Ubuntu Ubuntu=8.04
All of the following
ubuntu/linux-image-2.6.24-31-hppa32<2.6.24-31.99
2.6.24-31.99
Ubuntu Ubuntu=8.04
All of the following
ubuntu/linux-image-2.6.24-31-lpiacompat<2.6.24-31.99
2.6.24-31.99
Ubuntu Ubuntu=8.04
All of the following
ubuntu/linux-image-2.6.24-31-rt<2.6.24-31.99
2.6.24-31.99
Ubuntu Ubuntu=8.04
All of the following
ubuntu/linux-image-2.6.24-31-lpia<2.6.24-31.99
2.6.24-31.99
Ubuntu Ubuntu=8.04
All of the following
ubuntu/linux-image-2.6.24-31-generic<2.6.24-31.99
2.6.24-31.99
Ubuntu Ubuntu=8.04
All of the following
ubuntu/linux-image-2.6.24-31-hppa64<2.6.24-31.99
2.6.24-31.99
Ubuntu Ubuntu=8.04
All of the following
ubuntu/linux-image-2.6.24-31-mckinley<2.6.24-31.99
2.6.24-31.99
Ubuntu Ubuntu=8.04
All of the following
ubuntu/linux-image-2.6.24-31-xen<2.6.24-31.99
2.6.24-31.99
Ubuntu Ubuntu=8.04
All of the following
ubuntu/linux-image-2.6.24-31-powerpc64-smp<2.6.24-31.99
2.6.24-31.99
Ubuntu Ubuntu=8.04
All of the following
ubuntu/linux-image-2.6.24-31-itanium<2.6.24-31.99
2.6.24-31.99
Ubuntu Ubuntu=8.04
All of the following
ubuntu/linux-image-2.6.24-31-openvz<2.6.24-31.99
2.6.24-31.99
Ubuntu Ubuntu=8.04
All of the following
ubuntu/linux-image-2.6.24-31-386<2.6.24-31.99
2.6.24-31.99
Ubuntu Ubuntu=8.04
All of the following
ubuntu/linux-image-2.6.24-31-sparc64-smp<2.6.24-31.99
2.6.24-31.99
Ubuntu Ubuntu=8.04
All of the following
ubuntu/linux-image-2.6.24-31-powerpc-smp<2.6.24-31.99
2.6.24-31.99
Ubuntu Ubuntu=8.04

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade ubuntu/linux-image-2.6.24-31-powerpc to a version that resolves this vulnerability.

    Fixed in 2.6.24-31.99
  2. Upgrade

    Upgrade ubuntu/linux-image-2.6.24-31-sparc64 to a version that resolves this vulnerability.

    Fixed in 2.6.24-31.99
  3. Upgrade

    Upgrade ubuntu/linux-image-2.6.24-31-virtual to a version that resolves this vulnerability.

    Fixed in 2.6.24-31.99
  4. Upgrade

    Upgrade ubuntu/linux-image-2.6.24-31-server to a version that resolves this vulnerability.

    Fixed in 2.6.24-31.99
  5. Upgrade

    Upgrade ubuntu/linux-image-2.6.24-31-hppa32 to a version that resolves this vulnerability.

    Fixed in 2.6.24-31.99
  6. Upgrade

    Upgrade ubuntu/linux-image-2.6.24-31-lpiacompat to a version that resolves this vulnerability.

    Fixed in 2.6.24-31.99
  7. Upgrade

    Upgrade ubuntu/linux-image-2.6.24-31-rt to a version that resolves this vulnerability.

    Fixed in 2.6.24-31.99
  8. Upgrade

    Upgrade ubuntu/linux-image-2.6.24-31-lpia to a version that resolves this vulnerability.

    Fixed in 2.6.24-31.99
  9. Upgrade

    Upgrade ubuntu/linux-image-2.6.24-31-generic to a version that resolves this vulnerability.

    Fixed in 2.6.24-31.99
  10. Upgrade

    Upgrade ubuntu/linux-image-2.6.24-31-hppa64 to a version that resolves this vulnerability.

    Fixed in 2.6.24-31.99
  11. Upgrade

    Upgrade ubuntu/linux-image-2.6.24-31-mckinley to a version that resolves this vulnerability.

    Fixed in 2.6.24-31.99
  12. Upgrade

    Upgrade ubuntu/linux-image-2.6.24-31-xen to a version that resolves this vulnerability.

    Fixed in 2.6.24-31.99
  13. Upgrade

    Upgrade ubuntu/linux-image-2.6.24-31-powerpc64-smp to a version that resolves this vulnerability.

    Fixed in 2.6.24-31.99
  14. Upgrade

    Upgrade ubuntu/linux-image-2.6.24-31-itanium to a version that resolves this vulnerability.

    Fixed in 2.6.24-31.99
  15. Upgrade

    Upgrade ubuntu/linux-image-2.6.24-31-openvz to a version that resolves this vulnerability.

    Fixed in 2.6.24-31.99
  16. Upgrade

    Upgrade ubuntu/linux-image-2.6.24-31-386 to a version that resolves this vulnerability.

    Fixed in 2.6.24-31.99
  17. Upgrade

    Upgrade ubuntu/linux-image-2.6.24-31-sparc64-smp to a version that resolves this vulnerability.

    Fixed in 2.6.24-31.99
  18. Upgrade

    Upgrade ubuntu/linux-image-2.6.24-31-powerpc-smp to a version that resolves this vulnerability.

    Fixed in 2.6.24-31.99
  19. Upgrade

    Upgrade Linux kernel to a version that resolves this vulnerability.

    Patch USN-1390-1

Event History

Mar 6, 2012
Advisory Published
via Ubuntu·12:00 AM

Child vulnerabilities

Contains the following vulnerabilities.

Frequently Asked Questions

1

What is the severity of USN-1390-1?

The severity of USN-1390-1 is classified as a denial of service vulnerability.

2

Which systems are affected by USN-1390-1?

USN-1390-1 affects Ubuntu 8.04 systems running specific Linux kernel packages.

3

How do I fix USN-1390-1?

To fix USN-1390-1, you need to upgrade the affected Linux kernel packages to version 2.6.24-31.99.

4

Who reported the vulnerability USN-1390-1?

The vulnerabilities in USN-1390-1 were reported by Dan Rosenberg.

5

What types of attacks can exploit USN-1390-1?

USN-1390-1 can be exploited by a local attacker to cause a denial of service.

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