| 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: <2025072504-CVE-2025-38403-0da0@gregkh> Date: Fri, 25 Jul 2025 15:08:05 +0200 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...nel.org> Subject: CVE-2025-38403: vsock/vmci: Clear the vmci transport packet properly when initializing it From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: vsock/vmci: Clear the vmci transport packet properly when initializing it In vmci_transport_packet_init memset the vmci_transport_packet before populating the fields to avoid any uninitialised data being left in the structure. The Linux kernel CVE team has assigned CVE-2025-38403 to this issue. Affected and fixed versions =========================== Issue introduced in 3.9 with commit d021c344051af91f42c5ba9fdedc176740cbd238 and fixed in 5.4.296 with commit 19c2cc01ff9a8031398a802676ffb0f4692dd95d Issue introduced in 3.9 with commit d021c344051af91f42c5ba9fdedc176740cbd238 and fixed in 5.10.240 with commit 1c1bcb0e78230f533b4103e8cf271d17c3f469f0 Issue introduced in 3.9 with commit d021c344051af91f42c5ba9fdedc176740cbd238 and fixed in 5.15.187 with commit 2d44723a091bc853272e1a51a488a3d22b80be5e Issue introduced in 3.9 with commit d021c344051af91f42c5ba9fdedc176740cbd238 and fixed in 6.1.144 with commit 0a01021317375b8d1895152f544421ce49299eb1 Issue introduced in 3.9 with commit d021c344051af91f42c5ba9fdedc176740cbd238 and fixed in 6.6.97 with commit 94d0c326cb3ee6b0f8bd00e209550b93fcc5c839 Issue introduced in 3.9 with commit d021c344051af91f42c5ba9fdedc176740cbd238 and fixed in 6.12.37 with commit 75705b44e0b9aaa74f4c163d93d388bcba9e386a Issue introduced in 3.9 with commit d021c344051af91f42c5ba9fdedc176740cbd238 and fixed in 6.15.6 with commit e9a673153d578fd439919a24e99851b2f87ecbce Issue introduced in 3.9 with commit d021c344051af91f42c5ba9fdedc176740cbd238 and fixed in 6.16-rc5 with commit 223e2288f4b8c262a864e2c03964ffac91744cd5 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-2025-38403 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/vmci_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/19c2cc01ff9a8031398a802676ffb0f4692dd95d https://git.kernel.org/stable/c/1c1bcb0e78230f533b4103e8cf271d17c3f469f0 https://git.kernel.org/stable/c/2d44723a091bc853272e1a51a488a3d22b80be5e https://git.kernel.org/stable/c/0a01021317375b8d1895152f544421ce49299eb1 https://git.kernel.org/stable/c/94d0c326cb3ee6b0f8bd00e209550b93fcc5c839 https://git.kernel.org/stable/c/75705b44e0b9aaa74f4c163d93d388bcba9e386a https://git.kernel.org/stable/c/e9a673153d578fd439919a24e99851b2f87ecbce https://git.kernel.org/stable/c/223e2288f4b8c262a864e2c03964ffac91744cd5
Powered by blists - more mailing lists