CVE-2024-50264

Published Nov 19, 2024

Last updated 7 months ago

CVSS high 7.8
Linux Kernel

Overview

AI description

Automated description summarized from trusted sources.

CVE-2024-50264 is a vulnerability in the Linux kernel, specifically within the vsock/virtio subsystem. It arises from a dangling pointer issue during loopback communication. A dangling pointer can be created in `vsk->trans`, potentially leading to a Use-After-Free condition. The vulnerability occurs because the `vsk->trans` pointer is not properly initialized. The fix involves initializing `vsk->trans` to NULL, which prevents the use of the dangling pointer and resolves the Use-After-Free condition.

Description
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.
Source
416baaa9-dc9f-4396-8d5f-8c081fb06d67
NVD status
Modified
Products
linux_kernel

Risk scores

CVSS 3.1

Type
Primary
Base score
7.8
Impact score
5.9
Exploitability score
1.8
Vector string
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Severity
HIGH

Weaknesses

nvd@nist.gov
CWE-416
134c704f-9b21-4f2e-91b3-4a467353bcc0
CWE-416

Social media

Hype score
Not currently trending
  1. Race Condition Symphony: From Tiny Idea to Pwnie Slides from a talk by @v4bel and @_qwerty_po about exploiting CVE-2024-50264 — a race condition in the vsock subsystem. https://t.co/0ATZjFEet7 https://t.co/t1CsyPz5UH

    @linkersec

    25 Nov 2025

    1169 Impressions

    6 Retweets

    28 Likes

    13 Bookmarks

    1 Reply

    0 Quotes

  2. Kernel-hack-drill и новый эксплойт для CVE-2024-50264 в ядре Linux https://t.co/lHdHrLv5co https://t.co/YoG5XmldjN

    @VulnersHub

    3 Oct 2025

    0 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  3. Reduce the attack surface for CVE-2024-50264 without patching https://t.co/xFXXcDi3qV

    @vicariusltd

    16 Sept 2025

    100 Impressions

    0 Retweets

    1 Like

    0 Bookmarks

    0 Replies

    0 Quotes

  4. Linuxカーネル脆弱性CVE-2024-50264に対し、新たな権限昇格手法が公開された。従来は不安定なレース条件と複雑なメモリスプレーを要したが、研究者Alexander Popovはmsg_msgオブジェクトを利用し、安定したUAF悪用を

    @yousukezan

    9 Sept 2025

    1461 Impressions

    2 Retweets

    8 Likes

    1 Bookmark

    0 Replies

    0 Quotes

  5. Linuxカーネルの重大脆弱性CVE-2024-50264に対して、新たな攻撃手法が発見された。従来は困難とされたカーネルハードニングを突破し、権限昇格を現実的な脅威に変えた点で注目を集めている。 この脆弱性はLinu

    @yousukezan

    9 Sept 2025

    3234 Impressions

    7 Retweets

    19 Likes

    16 Bookmarks

    0 Replies

    0 Quotes

  6. Kernel-hack-drill and a new approach to exploiting CVE-2024-50264 in the Linux kernel #cybersecurity #linux https://t.co/sp0VgWbXyJ

    @davilagrau

    5 Sept 2025

    200 Impressions

    0 Retweets

    2 Likes

    1 Bookmark

    0 Replies

    0 Quotes

  7. Kernel-hack-drill and exploiting CVE-2024-50264 in the Linux kernel: https://t.co/R5KoUy1l3V #infosec #cybersecurity #tech #AI #linux

    @GothamJSharma

    3 Sept 2025

    145 Impressions

    0 Retweets

    1 Like

    0 Bookmarks

    0 Replies

    0 Quotes

  8. Kernel-hack-drill and a new approach to exploiting CVE-2024-50264 in the Linux kernel https://t.co/Zb1OPynINg

    @_r_netsec

    3 Sept 2025

    577 Impressions

    0 Retweets

    0 Likes

    1 Bookmark

    0 Replies

    0 Quotes

  9. Fascinating deep dive into exploiting a Linux kernel UAF vulnerability (CVE-2024-50264) 🔍. Even Hacker News readers are struggling to pull away! A must-read for security enthusiasts. #HackerNews #Tech 🐧 https://t.co/LthumtmvJp

    @thatkid02

    3 Sept 2025

    2 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  10. Kernel-hack-drill and exploiting CVE-2024-50264 in the Linux kernel #HackerNews https://t.co/pTTubrJsaM https://t.co/rPWbny9KZa

    @hackernewstop5

    3 Sept 2025

    96 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  11. My new article: "Kernel-hack-drill and a new approach to exploiting CVE-2024-50264 in the Linux kernel"⚡️ I tell a bug collision story and introduce my pet project kernel-hack-drill, which helped me to exploit the hard bug that received @PwnieAwards 2025 https://t.co/0DJzCJ

    @a13xp0p0v

    2 Sept 2025

    10136 Impressions

    56 Retweets

    165 Likes

    83 Bookmarks

    1 Reply

    0 Quotes

  12. New article by @a13xp0p0v: "Kernel-hack-drill and a new approach to exploiting CVE-2024-50264 in the Linux kernel." Alexander used his pet project kernel-hack-drill to exploit a hard race condition that received the Pwnie Award 2025. https://t.co/qiZwf1UvRe https://t.co/1zWley1

    @ptswarm

    2 Sept 2025

    2697 Impressions

    16 Retweets

    35 Likes

    9 Bookmarks

    0 Replies

    0 Quotes

  13. Top 5 Trending CVEs: 1 - CVE-2017-5689 2 - CVE-2025-31324 3 - CVE-2025-8088 4 - CVE-2025-4609 5 - CVE-2024-50264 #cve #cvetrends #cveshield #cybersecurity https://t.co/4Fua3CAN6W

    @CVEShield

    10 Aug 2025

    13 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  14. Our CVE-2024-50264 with @_qwerty_po has won the Best Privilege Escalation category at the 2025 Pwnie Awards. Thank you, @PwnieAwards!! https://t.co/zYEZFNT1Tv

    @v4bel

    9 Aug 2025

    5474 Impressions

    9 Retweets

    102 Likes

    14 Bookmarks

    7 Replies

    0 Quotes

  15. 🇰🇷 Our researcher @a13xp0p0v spoke at #Zer0Con2025 in Seoul, describing his experiments with CVE-2024-50264 in the Linux kernel involving his toolkit kernel-hack-drill. Huge respect 👏 Until next time! #LinuxSecurity https://t.co/Gebwo88bYy

    @PTsecurity_EN

    16 Apr 2025

    18 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

  16. Slides of my talk at #Zer0Con2025! ⚡️ Kernel-Hack-Drill: Environment For Developing Linux Kernel Exploits ⚡️ I presented the kernel-hack-drill open-source project and showed how it helped me to exploit CVE-2024-50264 in the Linux kernel. Enjoy! https://t.co/84DqT4rdvm https://

    @a13xp0p0v

    14 Apr 2025

    9680 Impressions

    70 Retweets

    232 Likes

    107 Bookmarks

    3 Replies

    2 Quotes

  17. kernelCTF VSock 0-day write-up by @v4bel @_qwerty_po (exp196/exp197, CVE-2024-50264) https://t.co/ChTa7JC8PR

    @alexjplaskett

    20 Jan 2025

    3205 Impressions

    8 Retweets

    87 Likes

    31 Bookmarks

    0 Replies

    0 Quotes

  18. kernelCTF VSock 0-day: CVE-2024-50264 by @v4bel and @_qwerty_po https://t.co/ChTa7JCGFp

    @alexjplaskett

    6 Jan 2025

    4465 Impressions

    22 Retweets

    105 Likes

    54 Bookmarks

    3 Replies

    0 Quotes

  19. I just released our kernelCTF VSock 0-day write-up with @_qwerty_po . (exp196/exp197, CVE-2024-50264) https://t.co/8UpGrVcDFF We made history by being the first to exploit VSock in kernelCTF, expanding its known attack vectors. 🥳 It’s a pretty *simple* race condition, right? h

    @v4bel

    19 Dec 2024

    12731 Impressions

    46 Retweets

    193 Likes

    85 Bookmarks

    6 Replies

    3 Quotes

  20. CVE-2024-50264 In the Linux kernel, the following vulnerability has been resolved: vsock/virtio: Initialization of the dangling pointer occurring in vsk->trans During loopback com… https://t.co/8odlWu3zoz

    @CVEnew

    19 Nov 2024

    557 Impressions

    0 Retweets

    0 Likes

    0 Bookmarks

    0 Replies

    0 Quotes

Configurations

  1. In the Linux kernel, the following vulnerability has been resolved: coresight: tmc-etr: Fix race condition between sysfs and perf mode When trying to run perf and sysfs mode simultaneously, the WARN_ON() in tmc_etr_enable_hw() is triggered sometimes: WARNING: CPU: 42 PID: 3911571 at drivers/hwtracing/coresight/coresight-tmc-etr.c:1060 tmc_etr_enable_hw+0xc0/0xd8 [coresight_tmc] [..snip..] Call trace: tmc_etr_enable_hw+0xc0/0xd8 [coresight_tmc] (P) tmc_enable_etr_sink+0x11c/0x250 [coresight_tmc] (L) tmc_enable_etr_sink+0x11c/0x250 [coresight_tmc] coresight_enable_path+0x1c8/0x218 [coresight] coresight_enable_sysfs+0xa4/0x228 [coresight] enable_source_store+0x58/0xa8 [coresight] dev_attr_store+0x20/0x40 sysfs_kf_write+0x4c/0x68 kernfs_fop_write_iter+0x120/0x1b8 vfs_write+0x2c8/0x388 ksys_write+0x74/0x108 __arm64_sys_write+0x24/0x38 el0_svc_common.constprop.0+0x64/0x148 do_el0_svc+0x24/0x38 el0_svc+0x3c/0x130 el0t_64_sync_handler+0xc8/0xd0 el0t_64_sync+0x1ac/0x1b0 ---[ end trace 0000000000000000 ]--- Since the enablement of sysfs mode is separeted into two critical regions, one for sysfs buffer allocation and another for hardware enablement, it's possible to race with the perf mode. Fix this by double check whether the perf mode's been used before enabling the hardware in sysfs mode. mode: [sysfs mode] [perf mode] tmc_etr_get_sysfs_buffer() spin_lock(&drvdata->spinlock) [sysfs buffer allocation] spin_unlock(&drvdata->spinlock) spin_lock(&drvdata->spinlock) tmc_etr_enable_hw() drvdata->etr_buf = etr_perf->etr_buf spin_unlock(&drvdata->spinlock) spin_lock(&drvdata->spinlock) tmc_etr_enable_hw() WARN_ON(drvdata->etr_buf) // WARN sicne etr_buf initialized at the perf side spin_unlock(&drvdata->spinlock) With this fix, we retain the check for CS_MODE_PERF in get_etr_sysfs_buf. This ensures we verify whether the perf mode's already running before we actually allocate the buffer. Then we can save the time of allocating/freeing the sysfs buffer if race with the perf mode.CVE-2026-46272