USN-1057-1: Linux kernel vulnerabilities

Published Feb 3, 2011
·
Updated

Dave Chinner discovered that the XFS filesystem did not correctly order inode lookups when exported by NFS. A remote attacker could exploit this to read or write disk blocks that had changed file assignment or had become unlinked, leading to a loss of privacy. (CVE-2010-2943) Dan Rosenberg discovered that several network ioctls did not clear kernel memory correctly. A local user could exploit this to read kernel stack memory, leading to a loss of privacy. (CVE-2010-3297) Kees Cook and Vasiliy Kulikov discovered that the shm interface did not clear kernel memory correctly. A local attacker could exploit this to read kernel stack memory, leading to a loss of privacy. (CVE-2010-4072)

Affected Software

44 affected componentsFixes available
All of the following
ubuntu/linux-image-2.6.15-55-hppa64<2.6.15-55.91
2.6.15-55.91
Ubuntu Ubuntu=6.06
All of the following
ubuntu/linux-image-2.6.15-55-mckinley<2.6.15-55.91
2.6.15-55.91
Ubuntu Ubuntu=6.06
All of the following
ubuntu/linux-image-2.6.15-55-powerpc-smp<2.6.15-55.91
2.6.15-55.91
Ubuntu Ubuntu=6.06
All of the following
ubuntu/linux-image-2.6.15-55-hppa32-smp<2.6.15-55.91
2.6.15-55.91
Ubuntu Ubuntu=6.06
All of the following
ubuntu/linux-image-2.6.15-55-686<2.6.15-55.91
2.6.15-55.91
Ubuntu Ubuntu=6.06
All of the following
ubuntu/linux-image-2.6.15-55-amd64-k8<2.6.15-55.91
2.6.15-55.91
Ubuntu Ubuntu=6.06
All of the following
ubuntu/linux-image-2.6.15-55-amd64-server<2.6.15-55.91
2.6.15-55.91
Ubuntu Ubuntu=6.06
All of the following
ubuntu/linux-image-2.6.15-55-386<2.6.15-55.91
2.6.15-55.91
Ubuntu Ubuntu=6.06
All of the following
ubuntu/linux-image-2.6.15-55-sparc64-smp<2.6.15-55.91
2.6.15-55.91
Ubuntu Ubuntu=6.06
All of the following
ubuntu/linux-image-2.6.15-55-k7<2.6.15-55.91
2.6.15-55.91
Ubuntu Ubuntu=6.06
All of the following
ubuntu/linux-image-2.6.15-55-sparc64<2.6.15-55.91
2.6.15-55.91
Ubuntu Ubuntu=6.06
All of the following
ubuntu/linux-image-2.6.15-55-server<2.6.15-55.91
2.6.15-55.91
Ubuntu Ubuntu=6.06
All of the following
ubuntu/linux-image-2.6.15-55-powerpc64-smp<2.6.15-55.91
2.6.15-55.91
Ubuntu Ubuntu=6.06
All of the following
ubuntu/linux-image-2.6.15-55-hppa32<2.6.15-55.91
2.6.15-55.91
Ubuntu Ubuntu=6.06
All of the following
ubuntu/linux-image-2.6.15-55-mckinley-smp<2.6.15-55.91
2.6.15-55.91
Ubuntu Ubuntu=6.06
All of the following
ubuntu/linux-image-2.6.15-55-server-bigiron<2.6.15-55.91
2.6.15-55.91
Ubuntu Ubuntu=6.06
All of the following
ubuntu/linux-image-2.6.15-55-itanium-smp<2.6.15-55.91
2.6.15-55.91
Ubuntu Ubuntu=6.06
All of the following
ubuntu/linux-image-2.6.15-55-amd64-xeon<2.6.15-55.91
2.6.15-55.91
Ubuntu Ubuntu=6.06
All of the following
ubuntu/linux-image-2.6.15-55-powerpc<2.6.15-55.91
2.6.15-55.91
Ubuntu Ubuntu=6.06
All of the following
ubuntu/linux-image-2.6.15-55-amd64-generic<2.6.15-55.91
2.6.15-55.91
Ubuntu Ubuntu=6.06
All of the following
ubuntu/linux-image-2.6.15-55-hppa64-smp<2.6.15-55.91
2.6.15-55.91
Ubuntu Ubuntu=6.06
All of the following
ubuntu/linux-image-2.6.15-55-itanium<2.6.15-55.91
2.6.15-55.91
Ubuntu Ubuntu=6.06

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade ubuntu/linux-image-2.6.15-55-hppa64 to a version that resolves this vulnerability.

    Fixed in 2.6.15-55.91
  2. Upgrade

    Upgrade ubuntu/linux-image-2.6.15-55-mckinley to a version that resolves this vulnerability.

    Fixed in 2.6.15-55.91
  3. Upgrade

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

    Fixed in 2.6.15-55.91
  4. Upgrade

    Upgrade ubuntu/linux-image-2.6.15-55-hppa32-smp to a version that resolves this vulnerability.

    Fixed in 2.6.15-55.91
  5. Upgrade

    Upgrade ubuntu/linux-image-2.6.15-55-686 to a version that resolves this vulnerability.

    Fixed in 2.6.15-55.91
  6. Upgrade

    Upgrade ubuntu/linux-image-2.6.15-55-amd64-k8 to a version that resolves this vulnerability.

    Fixed in 2.6.15-55.91
  7. Upgrade

    Upgrade ubuntu/linux-image-2.6.15-55-amd64-server to a version that resolves this vulnerability.

    Fixed in 2.6.15-55.91
  8. Upgrade

    Upgrade ubuntu/linux-image-2.6.15-55-386 to a version that resolves this vulnerability.

    Fixed in 2.6.15-55.91
  9. Upgrade

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

    Fixed in 2.6.15-55.91
  10. Upgrade

    Upgrade ubuntu/linux-image-2.6.15-55-k7 to a version that resolves this vulnerability.

    Fixed in 2.6.15-55.91
  11. Upgrade

    Upgrade ubuntu/linux-image-2.6.15-55-sparc64 to a version that resolves this vulnerability.

    Fixed in 2.6.15-55.91
  12. Upgrade

    Upgrade ubuntu/linux-image-2.6.15-55-server to a version that resolves this vulnerability.

    Fixed in 2.6.15-55.91
  13. Upgrade

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

    Fixed in 2.6.15-55.91
  14. Upgrade

    Upgrade ubuntu/linux-image-2.6.15-55-hppa32 to a version that resolves this vulnerability.

    Fixed in 2.6.15-55.91
  15. Upgrade

    Upgrade ubuntu/linux-image-2.6.15-55-mckinley-smp to a version that resolves this vulnerability.

    Fixed in 2.6.15-55.91
  16. Upgrade

    Upgrade ubuntu/linux-image-2.6.15-55-server-bigiron to a version that resolves this vulnerability.

    Fixed in 2.6.15-55.91
  17. Upgrade

    Upgrade ubuntu/linux-image-2.6.15-55-itanium-smp to a version that resolves this vulnerability.

    Fixed in 2.6.15-55.91
  18. Upgrade

    Upgrade ubuntu/linux-image-2.6.15-55-amd64-xeon to a version that resolves this vulnerability.

    Fixed in 2.6.15-55.91
  19. Upgrade

    Upgrade ubuntu/linux-image-2.6.15-55-powerpc to a version that resolves this vulnerability.

    Fixed in 2.6.15-55.91
  20. Upgrade

    Upgrade ubuntu/linux-image-2.6.15-55-amd64-generic to a version that resolves this vulnerability.

    Fixed in 2.6.15-55.91
  21. Upgrade

    Upgrade ubuntu/linux-image-2.6.15-55-hppa64-smp to a version that resolves this vulnerability.

    Fixed in 2.6.15-55.91
  22. Upgrade

    Upgrade ubuntu/linux-image-2.6.15-55-itanium to a version that resolves this vulnerability.

    Fixed in 2.6.15-55.91

Event History

Feb 3, 2011
Advisory Published
via Ubuntu·12:00 AM

Child vulnerabilities

Contains the following vulnerabilities.

Frequently Asked Questions

1

What is the severity of USN-1057-1?

USN-1057-1 addresses a medium severity vulnerability that allows remote attackers to read or write disk blocks.

2

How do I fix USN-1057-1?

To fix USN-1057-1, update the linux-image packages to version 2.6.15-55.91 or later.

3

Which Ubuntu versions are affected by USN-1057-1?

USN-1057-1 affects Ubuntu version 6.06.

4

What is the nature of the vulnerability in USN-1057-1?

The vulnerability in USN-1057-1 is related to incorrect ordering of inode lookups in the XFS filesystem when exported by NFS.

5

Can USN-1057-1 lead to data loss?

Yes, USN-1057-1 can lead to a loss of privacy as it allows attackers to manipulate disk blocks that have changed file assignment or become unlinked.

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