USN-6739-1: Linux kernel vulnerabilities

Published Apr 19, 2024
·
Updated

It was discovered that a race condition existed in the instruction emulator of the Linux kernel on Arm 64-bit systems. A local attacker could use this to cause a denial of service (system crash). (CVE-2022-20422) Wei Chen discovered that a race condition existed in the TIPC protocol implementation in the Linux kernel, leading to a null pointer dereference vulnerability. A local attacker could use this to cause a denial of service (system crash). (CVE-2023-1382) Jose Oliveira and Rodrigo Branco discovered that the Spectre Variant 2 mitigations with prctl syscall were insufficient in some situations. A local attacker could possibly use this to expose sensitive information. (CVE-2023-1998) Daniele Antonioli discovered that the Secure Simple Pairing and Secure Connections pairing in the Bluetooth protocol could allow an unauthenticated user to complete authentication without pairing credentials. A physically proximate attacker placed between two Bluetooth devices could use this to subsequently impersonate one of the paired devices. (CVE-2023-24023) shanzhulig discovered that the DRM subsystem in the Linux kernel contained a race condition when performing certain operation while handling driver unload, 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-51043) It was discovered that a race condition existed in the Bluetooth 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-51779) It was discovered that the device mapper driver in the Linux kernel did not properly validate target size during certain memory allocations. A local attacker could use this to cause a denial of service (system crash). (CVE-2023-52429, CVE-2024-23851) Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems:

Affected Software

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

    Fixed in Ubuntu Pro
  2. Upgrade

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

    Fixed in Ubuntu Pro
  3. Upgrade

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

    Fixed in Ubuntu Pro
  4. Upgrade

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

    Fixed in Ubuntu Pro
  5. Upgrade

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

    Fixed in Ubuntu Pro
  6. Upgrade

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

    Fixed in Ubuntu Pro
  7. Upgrade

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

    Fixed in Ubuntu Pro
  8. Upgrade

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

    Fixed in Ubuntu Pro
  9. Upgrade

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

    Fixed in Ubuntu Pro
  10. Upgrade

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

    Fixed in Ubuntu Pro
  11. Upgrade

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

    Fixed in Ubuntu Pro
  12. Upgrade

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

    Fixed in Ubuntu Pro
  13. Upgrade

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

    Fixed in Ubuntu Pro
  14. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Patch USN-6739-1

Event History

Apr 19, 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-6739-1?

The severity of USN-6739-1 is significant as it allows local attackers to cause a denial of service through a system crash.

2

How do I fix USN-6739-1?

To fix USN-6739-1, you should upgrade to the latest kernel version specified in the advisory.

3

Which systems are affected by USN-6739-1?

USN-6739-1 affects Ubuntu 16.04 systems running Arm 64-bit architecture.

4

What does the vulnerability USN-6739-1 affect?

The vulnerability USN-6739-1 affects the instruction emulator within the Linux kernel.

5

Is there a known exploit for USN-6739-1?

Currently, there are no publicly known exploits targeting the USN-6739-1 vulnerability.

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