USN-6602-1: Linux kernel vulnerabilities

Published Jan 25, 2024
·
Updated

Jana Hofmann, Emanuele Vannacci, Cedric Fournet, Boris Kopf, and Oleksii Oleksenko discovered that some AMD processors could leak stale data from division operations in certain situations. A local attacker could possibly use this to expose sensitive information. (CVE-2023-20588) It was discovered that a race condition existed in the Linux kernel when performing operations with kernel objects, leading to an out-of-bounds write. A local attacker could use this to cause a denial of service (system crash) or execute arbitrary code. (CVE-2023-45863) It was discovered that the CIFS network file system implementation in the Linux kernel did not properly validate the server frame size in certain situation, leading to an out-of-bounds read vulnerability. An attacker could use this to construct a malicious CIFS image that, when operated on, could cause a denial of service (system crash) or possibly expose sensitive information. (CVE-2023-6606) Budimir Markovic, Lucas De Marchi, and Pengfei Xu discovered that the perf subsystem in the Linux kernel did not properly validate all event sizes when attaching new events, leading to an out-of-bounds write vulnerability. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2023-6931) It was discovered that the IGMP protocol implementation in the Linux kernel contained a race condition, leading to a use-after-free vulnerability. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2023-6932)

Affected Software

34 affected componentsFixes available
All of the following
ubuntu/linux-image-4.4.0-1128-kvm<Ubuntu Pro
Ubuntu Pro
Ubuntu Ubuntu=16.04
All of the following
ubuntu/linux-image-4.4.0-250-generic<Ubuntu Pro
Ubuntu Pro
Ubuntu Ubuntu=16.04
All of the following
ubuntu/linux-image-4.4.0-250-lowlatency<Ubuntu Pro
Ubuntu Pro
Ubuntu Ubuntu=16.04
All of the following
ubuntu/linux-image-generic<Ubuntu Pro
Ubuntu Pro
Ubuntu Ubuntu=16.04
All of the following
ubuntu/linux-image-generic-lts-xenial<Ubuntu Pro
Ubuntu Pro
Ubuntu Ubuntu=16.04
All of the following
ubuntu/linux-image-kvm<Ubuntu Pro
Ubuntu Pro
Ubuntu Ubuntu=16.04
All of the following
ubuntu/linux-image-lowlatency<Ubuntu Pro
Ubuntu Pro
Ubuntu Ubuntu=16.04
All of the following
ubuntu/linux-image-lowlatency-lts-xenial<Ubuntu Pro
Ubuntu Pro
Ubuntu Ubuntu=16.04
All of the following
ubuntu/linux-image-virtual<Ubuntu Pro
Ubuntu Pro
Ubuntu Ubuntu=16.04
All of the following
ubuntu/linux-image-virtual-lts-xenial<Ubuntu Pro
Ubuntu Pro
Ubuntu Ubuntu=16.04
All of the following
ubuntu/linux-image-4.4.0-1127-aws<Ubuntu Pro
Ubuntu Pro
Ubuntu Ubuntu=14.04
All of the following
ubuntu/linux-image-4.4.0-250-generic<Ubuntu Pro
Ubuntu Pro
Ubuntu Ubuntu=14.04
All of the following
ubuntu/linux-image-4.4.0-250-lowlatency<Ubuntu Pro
Ubuntu Pro
Ubuntu Ubuntu=14.04
All of the following
ubuntu/linux-image-aws<Ubuntu Pro
Ubuntu Pro
Ubuntu Ubuntu=14.04
All of the following
ubuntu/linux-image-generic-lts-xenial<Ubuntu Pro
Ubuntu Pro
Ubuntu Ubuntu=14.04
All of the following
ubuntu/linux-image-lowlatency-lts-xenial<Ubuntu Pro
Ubuntu Pro
Ubuntu Ubuntu=14.04
All of the following
ubuntu/linux-image-virtual-lts-xenial<Ubuntu Pro
Ubuntu Pro
Ubuntu Ubuntu=14.04

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade ubuntu/linux-image-4.4.0-1128-kvm to a version that resolves this vulnerability.

    Fixed in Ubuntu Pro
  2. Upgrade

    Upgrade ubuntu/linux-image-4.4.0-250-generic to a version that resolves this vulnerability.

    Fixed in Ubuntu Pro
  3. Upgrade

    Upgrade ubuntu/linux-image-4.4.0-250-lowlatency to a version that resolves this vulnerability.

    Fixed in Ubuntu Pro
  4. Upgrade

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

    Fixed in Ubuntu Pro
  5. Upgrade

    Upgrade ubuntu/linux-image-generic-lts-xenial to a version that resolves this vulnerability.

    Fixed in Ubuntu Pro
  6. Upgrade

    Upgrade ubuntu/linux-image-kvm to a version that resolves this vulnerability.

    Fixed in Ubuntu Pro
  7. Upgrade

    Upgrade ubuntu/linux-image-lowlatency to a version that resolves this vulnerability.

    Fixed in Ubuntu Pro
  8. Upgrade

    Upgrade ubuntu/linux-image-lowlatency-lts-xenial to a version that resolves this vulnerability.

    Fixed in Ubuntu Pro
  9. Upgrade

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

    Fixed in Ubuntu Pro
  10. Upgrade

    Upgrade ubuntu/linux-image-virtual-lts-xenial to a version that resolves this vulnerability.

    Fixed in Ubuntu Pro
  11. Upgrade

    Upgrade ubuntu/linux-image-4.4.0-1127-aws to a version that resolves this vulnerability.

    Fixed in Ubuntu Pro
  12. Upgrade

    Upgrade ubuntu/linux-image-aws to a version that resolves this vulnerability.

    Fixed in Ubuntu Pro

Event History

Jan 25, 2024
Advisory Published
via Ubuntu·12:00 AM
Data Sourced
via Ubuntu·12:00 AM
DescriptionAffected Software

Child vulnerabilities

Contains the following vulnerabilities.

Frequently Asked Questions

1

What is the severity of USN-6602-1?

The severity of USN-6602-1 is considered high due to potential information leakage.

2

How do I fix USN-6602-1?

To fix USN-6602-1, update to the recommended kernel versions outlined in the advisory.

3

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

USN-6602-1 affects Ubuntu versions 14.04 and 16.04.

4

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

The vulnerability in USN-6602-1 allows local attackers to potentially leak sensitive data from AMD processors.

5

Is a system restart required after applying the fix for USN-6602-1?

Yes, a system restart is required to apply the kernel updates for USN-6602-1.

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