CVE-2024-50264: Linux kernel · vsock/virtio: Initialization of the dangling pointer occurring in vsk->trans
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 7.8 High · fixed in 4.15.0-1184.199~14.04.1 : patch Linux kernel soon.
Data as of 12 Nov 2026, 19:18 UTC
- Patch
- Available – fixed in 4.15.0-1184.199~14.04.1, 4.15.0-1176.189~16.04.1, 4.15.0-1184.199~16.04.1 +96
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 12 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Patches and advisories
- ubuntu.com/security/notices/USN-7167-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7169-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7170-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7173-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7169-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7173-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7179-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7179-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7185-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7186-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7167-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7169-3 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 24.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azure-6.11pkg:deb/ubuntu/linux-azure-6.11?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-gkepkg:deb/ubuntu/linux-gke?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available and has been released by Ubuntu in multiple kernel updates. Users should apply the security updates as provided in Ubuntu Security Notices USN-7167-1, USN-7169-1, and related advisories, and reboot their systems to ensure the fixes take effect. Due to an ABI change, recompilation and reinstallation of third-party kernel modules may be required. No additional mitigation steps are necessary beyond applying the official patches.
Description
CVE-2024-50264 is a high-severity vulnerability in the Linux kernel's vsock/virtio subsystem where a dangling pointer in vsk->trans can occur during loopback communication. This dangling pointer may lead to a Use-After-Free condition, potentially allowing an attacker with local privileges to compromise system confidentiality, integrity, and availability. The issue is resolved by initializing the pointer to NULL. Multiple Linux kernel versions, particularly various Ubuntu kernel builds prior to 4.15.0-1184 and some 4.11 and 4.13 versions, are affected. Official patches have been released and are available through Ubuntu security notices. Users should update and reboot to apply fixes.
References
- ubuntu.com/security/CVE-2024-50264 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2024-50264 (opens in a new tab)
- git.kernel.org/linus/6ca575374dd9a507cdd16dfa0e78c2e9e20bd05f (opens in a new tab)
- git.kernel.org/stable/c/5f092a4271f6dccf88fe0d132475a17b69ef71df (opens in a new tab)
- git.kernel.org/stable/c/fd8ae346692a56b4437d626c5460c7104980f389 (opens in a new tab)
- git.kernel.org/stable/c/eb1bdcb7dfc30b24495ee4c5533af0ed135cb5f1 (opens in a new tab)
- git.kernel.org/stable/c/2a6a4e69f255b7aed17f93995691ab4f0d3c2203 (opens in a new tab)
- git.kernel.org/stable/c/44d29897eafd0e1196453d3003a4d5e0b968eeab (opens in a new tab)
- git.kernel.org/stable/c/b110196fec44fe966952004bd426967c2a8fd358 (opens in a new tab)
- git.kernel.org/stable/c/5f970935d09934222fdef3d0e20c648ea7a963c1 (opens in a new tab)
- git.kernel.org/stable/c/6ca575374dd9a507cdd16dfa0e78c2e9e20bd05f (opens in a new tab)
- ubuntu.com/security/notices/USN-7167-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7169-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7170-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7173-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7169-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7173-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7179-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-7179-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-7185-1 (opens in a new tab)