| 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: <2024122717-CVE-2024-56572-b0fd@gregkh> Date: Fri, 27 Dec 2024 15:23:23 +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-56572: media: platform: allegro-dvt: Fix possible memory leak in allocate_buffers_internal() Description =========== In the Linux kernel, the following vulnerability has been resolved: media: platform: allegro-dvt: Fix possible memory leak in allocate_buffers_internal() The buffer in the loop should be released under the exception path, otherwise there may be a memory leak here. To mitigate this, free the buffer when allegro_alloc_buffer fails. The Linux kernel CVE team has assigned CVE-2024-56572 to this issue. Affected and fixed versions =========================== Issue introduced in 5.3 with commit f20387dfd065693ba7ea2788a2f893bf653c9cb8 and fixed in 5.4.287 with commit cf642904be39ae0d441dbdfa8f485e0a46260be4 Issue introduced in 5.3 with commit f20387dfd065693ba7ea2788a2f893bf653c9cb8 and fixed in 5.10.231 with commit 74a65313578b35e1239966adfa7ac2bdd60caf00 Issue introduced in 5.3 with commit f20387dfd065693ba7ea2788a2f893bf653c9cb8 and fixed in 5.15.174 with commit 64f72a738864b506ab50b4a6cb3ce3c3e04b71af Issue introduced in 5.3 with commit f20387dfd065693ba7ea2788a2f893bf653c9cb8 and fixed in 6.1.120 with commit 17e5613666209be4e5be1f1894f1a6014a8a0658 Issue introduced in 5.3 with commit f20387dfd065693ba7ea2788a2f893bf653c9cb8 and fixed in 6.6.64 with commit 6712a28a4f923ffdf51cff267ad05a634ee1babc Issue introduced in 5.3 with commit f20387dfd065693ba7ea2788a2f893bf653c9cb8 and fixed in 6.12.4 with commit 891b5790bee8fc6ddba17874dd87a646128d0b99 Issue introduced in 5.3 with commit f20387dfd065693ba7ea2788a2f893bf653c9cb8 and fixed in 6.13-rc1 with commit 0f514068fbc5d4d189c817adc7c4e32cffdc2e47 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-56572 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: drivers/media/platform/allegro-dvt/allegro-core.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/cf642904be39ae0d441dbdfa8f485e0a46260be4 https://git.kernel.org/stable/c/74a65313578b35e1239966adfa7ac2bdd60caf00 https://git.kernel.org/stable/c/64f72a738864b506ab50b4a6cb3ce3c3e04b71af https://git.kernel.org/stable/c/17e5613666209be4e5be1f1894f1a6014a8a0658 https://git.kernel.org/stable/c/6712a28a4f923ffdf51cff267ad05a634ee1babc https://git.kernel.org/stable/c/891b5790bee8fc6ddba17874dd87a646128d0b99 https://git.kernel.org/stable/c/0f514068fbc5d4d189c817adc7c4e32cffdc2e47
Powered by blists - more mailing lists