CVE-2024-50264: vsock/virtio: Initialization of the dangling pointer occurring in vsk->trans

Published Nov 19, 2024
·
Updated

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

vsock/virtio: Initialization of the dangling pointer occurring in vsk->trans

During loopback communication, a dangling pointer can be created in vsk->trans, potentially leading to a Use-After-Free condition. This issue is resolved by initializing vsk->trans to NULL.

Other sources

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

21 affected componentsFixes available
Linux Linux kernel>=4.8<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-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
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
Google Android
Microsoft cbl2 kernel 5.15.167.1-2
Microsoft azl3 kernel 6.6.64.2-1
Microsoft cbl2 kernel 5.15.173.1-1
Microsoft azl3 kernel 6.6.57.1-7
Microsoft cbl2 kernel 5.15.167.1-2

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
  3. Configuration

    Resolve the potential dangling pointer/use-after-free during loopback communication by initializing vsk->trans to NULL.

    Linux kernel (vsock/virtio) vsk->trans initialization = NULL

Event History

Nov 19, 2024
CVE Published
via MITRE·01:29 AM
Data Sourced
via MITRE·01:29 AM
DescriptionSeverity
Data Sourced
via Red Hat·02:01 AM
DescriptionSeverityAffected Software
Data Sourced
via NVD·02:16 AM
RemedyDescriptionSeverityWeaknessAffected Software
Dec 12, 2024
Data Sourced
via Microsoft·08:00 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·08:00 AM
Affected Software
Updated
via Microsoft·08:00 AM
Affected Software
Updated
via Microsoft·08:00 AM
SeverityAffected Software
Updated
via Microsoft·08:00 AM
DescriptionSeverity
Dec 17, 2024
Data Sourced
via Launchpad·08:14 PM
Description
Apr 7, 2025
Data Sourced
via Android·12:00 AM
SeverityWeaknessAffected Software
Apr 29, 2025
Data Sourced
via Ubuntu·06:31 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-50264?

CVE-2024-50264 is classified as a high-severity vulnerability due to the potential for a Use-After-Free condition.

2

How do I fix CVE-2024-50264?

To fix CVE-2024-50264, update the Linux kernel to versions 6.1.123-1, 6.1.119-1, or higher.

3

Which versions of the Linux kernel are affected by CVE-2024-50264?

CVE-2024-50264 affects Linux kernel versions from 4.8 to 6.11.8, as well as specific release candidates.

4

Is CVE-2024-50264 related to loopback communication?

Yes, CVE-2024-50264 involves a dangling pointer created during loopback communication in the Linux kernel.

5

What are the potential consequences of CVE-2024-50264?

Users impacted by CVE-2024-50264 may experience system instability or crashes due to the Use-After-Free condition.

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