| 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: <2025050819-CVE-2025-37817-d85c@gregkh> Date: Thu, 8 May 2025 08:39:26 +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-37817: mcb: fix a double free bug in chameleon_parse_gdd() From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: mcb: fix a double free bug in chameleon_parse_gdd() In chameleon_parse_gdd(), if mcb_device_register() fails, 'mdev' would be released in mcb_device_register() via put_device(). Thus, goto 'err' label and free 'mdev' again causes a double free. Just return if mcb_device_register() fails. The Linux kernel CVE team has assigned CVE-2025-37817 to this issue. Affected and fixed versions =========================== Issue introduced in 3.15 with commit 3764e82e5150d87b205c10cd78a9c9ab86fbfa51 and fixed in 5.4.293 with commit d70184958b0ea8c0fd52e2b456654b503e769fc8 Issue introduced in 3.15 with commit 3764e82e5150d87b205c10cd78a9c9ab86fbfa51 and fixed in 5.10.237 with commit 4ffe8c9fb561e4427dd1a3056cd5b3685b74f78d Issue introduced in 3.15 with commit 3764e82e5150d87b205c10cd78a9c9ab86fbfa51 and fixed in 5.15.181 with commit 59f993cd36b6e28a394ba3d977e8ffe5c9884e3b Issue introduced in 3.15 with commit 3764e82e5150d87b205c10cd78a9c9ab86fbfa51 and fixed in 6.1.136 with commit c5b8a549ef1fcc6066b037a3962c79d60465ba0b Issue introduced in 3.15 with commit 3764e82e5150d87b205c10cd78a9c9ab86fbfa51 and fixed in 6.6.89 with commit 96838eb1836fd372e42be5db84f0b333b65146a6 Issue introduced in 3.15 with commit 3764e82e5150d87b205c10cd78a9c9ab86fbfa51 and fixed in 6.12.26 with commit df1a5d5c6134224f9298e5189230f9d29ae50cac Issue introduced in 3.15 with commit 3764e82e5150d87b205c10cd78a9c9ab86fbfa51 and fixed in 6.14.5 with commit bcc7d58ee5173e34306026bd01e1fbf75e169d37 Issue introduced in 3.15 with commit 3764e82e5150d87b205c10cd78a9c9ab86fbfa51 and fixed in 6.15-rc4 with commit 7c7f1bfdb2249f854a736d9b79778c7e5a29a150 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-37817 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/mcb/mcb-parse.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/d70184958b0ea8c0fd52e2b456654b503e769fc8 https://git.kernel.org/stable/c/4ffe8c9fb561e4427dd1a3056cd5b3685b74f78d https://git.kernel.org/stable/c/59f993cd36b6e28a394ba3d977e8ffe5c9884e3b https://git.kernel.org/stable/c/c5b8a549ef1fcc6066b037a3962c79d60465ba0b https://git.kernel.org/stable/c/96838eb1836fd372e42be5db84f0b333b65146a6 https://git.kernel.org/stable/c/df1a5d5c6134224f9298e5189230f9d29ae50cac https://git.kernel.org/stable/c/bcc7d58ee5173e34306026bd01e1fbf75e169d37 https://git.kernel.org/stable/c/7c7f1bfdb2249f854a736d9b79778c7e5a29a150
Powered by blists - more mailing lists