USN-6700-1: Linux kernel vulnerabilities

Published Mar 18, 2024
·
Updated

It was discovered that the Layer 2 Tunneling Protocol (L2TP) implementation in the Linux kernel contained a race condition when releasing PPPoL2TP sockets in certain conditions, 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-2022-20567) It was discovered that the ext4 file system implementation in the Linux kernel did not properly handle block device modification while it is mounted. A privileged attacker could use this to cause a denial of service (system crash) or possibly expose sensitive information. (CVE-2023-34256) Eric Dumazet discovered that the netfilter subsystem in the Linux kernel did not properly handle DCCP conntrack buffers in certain situations, leading to an out-of-bounds read vulnerability. An attacker could possibly use this to expose sensitive information (kernel memory). (CVE-2023-39197) It was discovered that a race condition existed in the AppleTalk networking subsystem of the Linux kernel, 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-51781) It was discovered that the ext4 file system implementation in the Linux kernel did not properly handle the remount operation in certain cases, leading to a use-after-free vulnerability. A local attacker could use this to cause a denial of service (system crash) or possibly expose sensitive information. (CVE-2024-0775) Notselwyn discovered that the netfilter subsystem in the Linux kernel did not properly handle verdict parameters in certain cases, 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-2024-1086) It was discovered that a race condition existed in the SCSI Emulex LightPulse Fibre Channel driver in the Linux kernel when unregistering FCF and re-scanning an HBA FCF table, leading to a null pointer dereference vulnerability. A local attacker could use this to cause a denial of service (system crash). (CVE-2024-24855)

Affected Software

34 affected componentsFixes available
All of the following
ubuntu/linux-image-4.4.0-1130-kvm<Ubuntu Pro
Ubuntu Pro
Ubuntu Ubuntu=16.04
All of the following
ubuntu/linux-image-4.4.0-252-generic<Ubuntu Pro
Ubuntu Pro
Ubuntu Ubuntu=16.04
All of the following
ubuntu/linux-image-4.4.0-252-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-1129-aws<Ubuntu Pro
Ubuntu Pro
Ubuntu Ubuntu=14.04
All of the following
ubuntu/linux-image-4.4.0-252-generic<Ubuntu Pro
Ubuntu Pro
Ubuntu Ubuntu=14.04
All of the following
ubuntu/linux-image-4.4.0-252-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-1130-kvm to a version that resolves this vulnerability.

    Fixed in Ubuntu Pro
  2. Upgrade

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

    Fixed in Ubuntu Pro
  3. Upgrade

    Upgrade ubuntu/linux-image-4.4.0-252-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-1129-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

Mar 18, 2024
Advisory Published
via Ubuntu·12:00 AM
Data Sourced
via Ubuntu·12:00 AM
DescriptionAffected Software

Frequently Asked Questions

1

What is the severity of USN-6700-1?

The severity of USN-6700-1 is considered high due to the potential for local attackers to cause a denial of service by exploiting the use-after-free vulnerability.

2

How do I fix USN-6700-1?

To fix USN-6700-1, upgrade to the recommended package versions such as linux-image-4.4.0-1130.140 or linux-image-4.4.0-252.286 for Ubuntu 16.04.

3

What causes the vulnerability in USN-6700-1?

The vulnerability in USN-6700-1 is caused by a race condition when releasing PPPoL2TP sockets within the L2TP implementation in the Linux kernel.

4

Who is affected by USN-6700-1?

USN-6700-1 affects local user accounts on systems running specific versions of Ubuntu 14.04 and 16.04 with the vulnerable kernel packages.

5

What protections are in place against USN-6700-1 exploitation?

While there are no specific protections against this exploit, keeping your system updated and applying recommended patches can help mitigate risks.

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