| From bippy-5f407fcff5a0 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@linuxfoundation.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2024-53103: hv_sock: Initializing vsk->trans to NULL to prevent a dangling pointer |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| hv_sock: 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. |
| |
| The Linux kernel CVE team has assigned CVE-2024-53103 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 4.14 with commit ae0078fcf0a5eb3a8623bfb5f988262e0911fdb9 and fixed in 4.19.324 with commit 285266ef92f7b4bf7d26e1e95e215ce6a6badb4a |
| Issue introduced in 4.14 with commit ae0078fcf0a5eb3a8623bfb5f988262e0911fdb9 and fixed in 5.4.286 with commit 4fe1d42f2acc463b733bb42e3f8e67dbc2a0eb2d |
| Issue introduced in 4.14 with commit ae0078fcf0a5eb3a8623bfb5f988262e0911fdb9 and fixed in 5.10.230 with commit 414476c4fb11be070c09ab8f3e75c9ee324a108a |
| Issue introduced in 4.14 with commit ae0078fcf0a5eb3a8623bfb5f988262e0911fdb9 and fixed in 5.15.172 with commit 7cf25987820350cb950856c71b409e5b6eed52bd |
| Issue introduced in 4.14 with commit ae0078fcf0a5eb3a8623bfb5f988262e0911fdb9 and fixed in 6.1.117 with commit 98d8dde9232250a57ad5ef16479bf6a349e09b80 |
| Issue introduced in 4.14 with commit ae0078fcf0a5eb3a8623bfb5f988262e0911fdb9 and fixed in 6.6.61 with commit 4bdc5a62c6e50600d8a1c3e18fd6dce0c27c9497 |
| Issue introduced in 4.14 with commit ae0078fcf0a5eb3a8623bfb5f988262e0911fdb9 and fixed in 6.11.8 with commit e0fe3392371293175f25028020ded5267f4cd8e3 |
| Issue introduced in 4.14 with commit ae0078fcf0a5eb3a8623bfb5f988262e0911fdb9 and fixed in 6.12.1 with commit 8621725afb38e111969c64280b71480afde2aace |
| Issue introduced in 4.14 with commit ae0078fcf0a5eb3a8623bfb5f988262e0911fdb9 and fixed in 6.13 with commit e629295bd60abf4da1db85b82819ca6a4f6c1e79 |
| |
| 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-53103 |
| 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/hyperv_transport.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/285266ef92f7b4bf7d26e1e95e215ce6a6badb4a |
| https://git.kernel.org/stable/c/4fe1d42f2acc463b733bb42e3f8e67dbc2a0eb2d |
| https://git.kernel.org/stable/c/414476c4fb11be070c09ab8f3e75c9ee324a108a |
| https://git.kernel.org/stable/c/7cf25987820350cb950856c71b409e5b6eed52bd |
| https://git.kernel.org/stable/c/98d8dde9232250a57ad5ef16479bf6a349e09b80 |
| https://git.kernel.org/stable/c/4bdc5a62c6e50600d8a1c3e18fd6dce0c27c9497 |
| https://git.kernel.org/stable/c/e0fe3392371293175f25028020ded5267f4cd8e3 |
| https://git.kernel.org/stable/c/8621725afb38e111969c64280b71480afde2aace |
| https://git.kernel.org/stable/c/e629295bd60abf4da1db85b82819ca6a4f6c1e79 |
