CVE-2024-53103: hv_sock: Initializing vsk->trans to NULL to prevent a dangling pointer

Published Dec 2, 2024
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

hvsock: Initializing vsk->trans to NULL to prevent a dangling pointer

When hvs is released, there is a possibility that vsk->trans may not be initialized to NULL, which could lead to a dangling pointer. This issue is resolved by initializing vsk->trans to NULL.

Other sources

In the Linux kernel, the following vulnerability has been resolved:

hvsock: Initializing vsk->trans to NULL to prevent a dangling pointer

When hvs is released, there is a possibility that vsk->trans may not be initialized to NULL, which could lead to a dangling pointer. This issue is resolved by initializing vsk->trans to NULL.

NVD

This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.

Launchpad

Affected Software

17 affected componentsFixes available
Linux Linux kernel<4.19.324
Linux Linux kernel>=4.20<5.4.286
Linux Linux kernel>=5.5<5.10.230
Linux Linux kernel>=5.11<5.15.172
Linux Linux kernel>=5.16<6.1.117
Linux Linux kernel>=6.2<6.6.61
Linux Linux kernel>=6.7<6.11.8
Linux Linux kernel=6.12
Linux Linux kernel=6.12-rc1
Linux Linux kernel=6.12-rc2
Linux Linux kernel=6.12-rc3
Linux Linux kernel=6.12-rc4
Linux Linux kernel=6.12-rc5
Linux Linux kernel=6.12-rc6
Linux Linux kernel=6.12-rc7
debian/linux<=5.10.223-1
5.10.234-16.1.129-16.1.135-16.12.27-1
debian/linux-6.1
6.1.129-1~deb11u1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.27-1
  2. Upgrade

    Upgrade debian/linux-6.1 to a version that resolves this vulnerability.

    Fixed in 6.1.129-1~deb11u1

Event History

Dec 2, 2024
CVE Published
via MITRE·07:29 AM
Data Sourced
via MITRE·07:29 AM
DescriptionSeverity
Data Sourced
via Red Hat·08:01 AM
DescriptionSeverityAffected Software
Data Sourced
via NVD·08:15 AM
RemedyDescriptionSeverityWeaknessAffected Software
Jan 28, 2025
Data Sourced
via Launchpad·08:57 PM
Description
May 1, 2025
Data Sourced
via Ubuntu·12:37 AM
RemedyDescriptionSeverityAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-53103?

CVE-2024-53103 has been classified as a severity level that requires attention due to potential risks associated with dangling pointers in the Linux kernel.

2

How do I fix CVE-2024-53103?

To fix CVE-2024-53103, ensure to update your Linux kernel to one of the patched versions, such as 6.1.123-1 or 6.12.11-1.

3

Which Linux kernel versions are affected by CVE-2024-53103?

CVE-2024-53103 affects Linux kernel versions prior to 5.10.223-1 and various other versions between 4.19 and the latest releases.

4

What are the potential impacts of not addressing CVE-2024-53103?

Failing to address CVE-2024-53103 may lead to system instability, security vulnerabilities, and potential exploitation through dangling pointers.

5

Is my version of Linux kernel vulnerable to CVE-2024-53103?

You are vulnerable to CVE-2024-53103 if you are running a version of the Linux kernel between 4.19 and 5.10.223-1 or any other affected version.

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