| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <2024111920-CVE-2024-50264-0889@gregkh> Date: Tue, 19 Nov 2024 02:32:19 +0100 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org> Subject: CVE-2024-50264: vsock/virtio: Initialization of the dangling pointer occurring in vsk->trans 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. The Linux kernel CVE team has assigned CVE-2024-50264 to this issue. Affected and fixed versions =========================== Issue introduced in 4.8 with commit 06a8fc78367d and fixed in 4.19.324 with commit 5f092a4271f6 Issue introduced in 4.8 with commit 06a8fc78367d and fixed in 5.4.286 with commit fd8ae346692a Issue introduced in 4.8 with commit 06a8fc78367d and fixed in 5.10.230 with commit eb1bdcb7dfc3 Issue introduced in 4.8 with commit 06a8fc78367d and fixed in 5.15.172 with commit 2a6a4e69f255 Issue introduced in 4.8 with commit 06a8fc78367d and fixed in 6.1.117 with commit 44d29897eafd Issue introduced in 4.8 with commit 06a8fc78367d and fixed in 6.6.61 with commit b110196fec44 Issue introduced in 4.8 with commit 06a8fc78367d and fixed in 6.11.8 with commit 5f970935d099 Issue introduced in 4.8 with commit 06a8fc78367d and fixed in 6.12 with commit 6ca575374dd9 Please see https://www.kernel.org for a full list of currently supported kernel versions by the kernel community. Unaffected versions might change over time as fixes are backported to older supported kernel versions. The official CVE entry at https://cve.org/CVERecord/?id=CVE-2024-50264 will be updated if fixes are backported, please check that for the most up to date information about this issue. Affected files ============== The file(s) affected by this issue are: net/vmw_vsock/virtio_transport_common.c Mitigation ========== The Linux kernel CVE team recommends that you update to the latest stable kernel version for this, and many other bugfixes. Individual changes are never tested alone, but rather are part of a larger kernel release. Cherry-picking individual commits is not recommended or supported by the Linux kernel community at all. If however, updating to the latest release is impossible, the individual changes to resolve this issue can be found at these commits: https://git.kernel.org/stable/c/5f092a4271f6dccf88fe0d132475a17b69ef71df https://git.kernel.org/stable/c/fd8ae346692a56b4437d626c5460c7104980f389 https://git.kernel.org/stable/c/eb1bdcb7dfc30b24495ee4c5533af0ed135cb5f1 https://git.kernel.org/stable/c/2a6a4e69f255b7aed17f93995691ab4f0d3c2203 https://git.kernel.org/stable/c/44d29897eafd0e1196453d3003a4d5e0b968eeab https://git.kernel.org/stable/c/b110196fec44fe966952004bd426967c2a8fd358 https://git.kernel.org/stable/c/5f970935d09934222fdef3d0e20c648ea7a963c1 https://git.kernel.org/stable/c/6ca575374dd9a507cdd16dfa0e78c2e9e20bd05f
Powered by blists - more mailing lists