| 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: <2025072556-CVE-2025-38428-8b33@gregkh> Date: Fri, 25 Jul 2025 16:17:01 +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-38428: Input: ims-pcu - check record size in ims_pcu_flash_firmware() From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: Input: ims-pcu - check record size in ims_pcu_flash_firmware() The "len" variable comes from the firmware and we generally do trust firmware, but it's always better to double check. If the "len" is too large it could result in memory corruption when we do "memcpy(fragment->data, rec->data, len);" The Linux kernel CVE team has assigned CVE-2025-38428 to this issue. Affected and fixed versions =========================== Issue introduced in 3.10 with commit 628329d52474323938a03826941e166bc7c8eff4 and fixed in 5.4.295 with commit c1b9d140b0807c6aee4bb53e1bfa4e391e3dc204 Issue introduced in 3.10 with commit 628329d52474323938a03826941e166bc7c8eff4 and fixed in 5.10.239 with commit d63706d9f73846106fde28b284f08e01b92ce9f1 Issue introduced in 3.10 with commit 628329d52474323938a03826941e166bc7c8eff4 and fixed in 5.15.186 with commit e5a2481dc2a0b430f49276d7482793a8923631d6 Issue introduced in 3.10 with commit 628329d52474323938a03826941e166bc7c8eff4 and fixed in 6.1.142 with commit 8e03f1c7d50343bf21da54873301bc4fa647479f Issue introduced in 3.10 with commit 628329d52474323938a03826941e166bc7c8eff4 and fixed in 6.6.95 with commit 17474a56acf708bf6b2d174c06ed26abad0a9fd6 Issue introduced in 3.10 with commit 628329d52474323938a03826941e166bc7c8eff4 and fixed in 6.12.35 with commit 5a8cd6ae8393e2eaebf51d420d5374821ef2af87 Issue introduced in 3.10 with commit 628329d52474323938a03826941e166bc7c8eff4 and fixed in 6.15.4 with commit 74661516daee1eadebede8dc607b6830530096ec Issue introduced in 3.10 with commit 628329d52474323938a03826941e166bc7c8eff4 and fixed in 6.16-rc1 with commit a95ef0199e80f3384eb992889322957d26c00102 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-38428 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/input/misc/ims-pcu.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/c1b9d140b0807c6aee4bb53e1bfa4e391e3dc204 https://git.kernel.org/stable/c/d63706d9f73846106fde28b284f08e01b92ce9f1 https://git.kernel.org/stable/c/e5a2481dc2a0b430f49276d7482793a8923631d6 https://git.kernel.org/stable/c/8e03f1c7d50343bf21da54873301bc4fa647479f https://git.kernel.org/stable/c/17474a56acf708bf6b2d174c06ed26abad0a9fd6 https://git.kernel.org/stable/c/5a8cd6ae8393e2eaebf51d420d5374821ef2af87 https://git.kernel.org/stable/c/74661516daee1eadebede8dc607b6830530096ec https://git.kernel.org/stable/c/a95ef0199e80f3384eb992889322957d26c00102
Powered by blists - more mailing lists