USN-5756-2: Linux kernel (GKE) vulnerabilities

Published Dec 2, 2022
·
Updated

Jann Horn discovered that the Linux kernel did not properly track memory allocations for anonymous VMA mappings in some situations, leading to potential data structure reuse. A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2022-42703) It was discovered that a memory leak existed in the IPv6 implementation of the Linux kernel. A local attacker could use this to cause a denial of service (memory exhaustion). (CVE-2022-3524) It was discovered that a race condition existed in the Bluetooth subsystem in 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-2022-3564) It was discovered that the ISDN implementation of the Linux kernel contained a use-after-free vulnerability. A privileged user could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2022-3565) It was discovered that the TCP implementation in the Linux kernel contained a data race condition. An attacker could possibly use this to cause undesired behaviors. (CVE-2022-3566) It was discovered that the IPv6 implementation in the Linux kernel contained a data race condition. An attacker could possibly use this to cause undesired behaviors. (CVE-2022-3567) It was discovered that the Realtek RTL8152 USB Ethernet adapter driver in the Linux kernel did not properly handle certain error conditions. A local attacker with physical access could plug in a specially crafted USB device to cause a denial of service (memory exhaustion). (CVE-2022-3594) It was discovered that a null pointer dereference existed in the NILFS2 file system implementation in the Linux kernel. A local attacker could use this to cause a denial of service (system crash). (CVE-2022-3621)

Affected Software

1 affected component
Canonical Linux kernel (GKE)

Event History

May 10, 2025
Advisory Published
via Ubuntu·03:55 AM
Data Sourced
via Ubuntu·03:55 AM
DescriptionAffected Software

Frequently Asked Questions

1

What is the severity of USN-5756-2?

The severity of USN-5756-2 is high.

2

How do I fix USN-5756-2?

To fix USN-5756-2, update to the latest version of the Linux kernel package specified in the Ubuntu security advisory.

3

Is there a known exploit for USN-5756-2?

There are currently no known exploits for USN-5756-2.

4

Which software versions are affected by USN-5756-2?

USN-5756-2 affects Ubuntu 20.04 with the specified versions of the Linux kernel packages.

5

Where can I find more information about USN-5756-2?

You can find more information about USN-5756-2 in the Ubuntu security advisory referenced in the description.

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