| 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: <2024111906-CVE-2024-50300-a5c0@gregkh> Date: Tue, 19 Nov 2024 02:32:55 +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-50300: regulator: rtq2208: Fix uninitialized use of regulator_config Description =========== In the Linux kernel, the following vulnerability has been resolved: regulator: rtq2208: Fix uninitialized use of regulator_config Fix rtq2208 driver uninitialized use to cause kernel error. The Linux kernel CVE team has assigned CVE-2024-50300 to this issue. Affected and fixed versions =========================== Issue introduced in 6.6 with commit 85a11f55621a and fixed in 6.6.61 with commit 9b7c0405af66 Issue introduced in 6.6 with commit 85a11f55621a and fixed in 6.11.8 with commit 64fbab934ae5 Issue introduced in 6.6 with commit 85a11f55621a and fixed in 6.12 with commit 2feb02311084 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-50300 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/regulator/rtq2208-regulator.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/9b7c0405af667857b3ad24a7ef6723f5475a9e43 https://git.kernel.org/stable/c/64fbab934ae59be9caffc80a75450984b1e108e0 https://git.kernel.org/stable/c/2feb023110843acce790e9089e72e9a9503d9fa5
Powered by blists - more mailing lists