| 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: <2025022613-CVE-2022-49608-3814@gregkh> Date: Wed, 26 Feb 2025 03:22:51 +0100 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org> Subject: CVE-2022-49608: pinctrl: ralink: Check for null return of devm_kcalloc Description =========== In the Linux kernel, the following vulnerability has been resolved: pinctrl: ralink: Check for null return of devm_kcalloc Because of the possible failure of the allocation, data->domains might be NULL pointer and will cause the dereference of the NULL pointer later. Therefore, it might be better to check it and directly return -ENOMEM without releasing data manually if fails, because the comment of the devm_kmalloc() says "Memory allocated with this function is automatically freed on driver detach.". The Linux kernel CVE team has assigned CVE-2022-49608 to this issue. Affected and fixed versions =========================== Issue introduced in 4.18 with commit a86854d0c599b3202307abceb68feee4d7061578 and fixed in 4.19.254 with commit 13596e6c9e541e90e5fc2c52b23f08b951370da9 Issue introduced in 4.18 with commit a86854d0c599b3202307abceb68feee4d7061578 and fixed in 5.4.208 with commit 6194c021496addc11763d1ffa89ce5751889fe3c Issue introduced in 4.18 with commit a86854d0c599b3202307abceb68feee4d7061578 and fixed in 5.10.134 with commit 5694b162f275fb9a9f89422701b2b963be11e496 Issue introduced in 4.18 with commit a86854d0c599b3202307abceb68feee4d7061578 and fixed in 5.15.58 with commit 44016a85419ca0d4f1e4d0127b330f8e4e2a57d0 Issue introduced in 4.18 with commit a86854d0c599b3202307abceb68feee4d7061578 and fixed in 5.18.15 with commit 5595d30c4dc27d939635c3188c68203b6ece1711 Issue introduced in 4.18 with commit a86854d0c599b3202307abceb68feee4d7061578 and fixed in 5.19 with commit c3b821e8e406d5650e587b7ac624ac24e9b780a8 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-2022-49608 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/pinctrl/ralink/pinctrl-ralink.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/13596e6c9e541e90e5fc2c52b23f08b951370da9 https://git.kernel.org/stable/c/6194c021496addc11763d1ffa89ce5751889fe3c https://git.kernel.org/stable/c/5694b162f275fb9a9f89422701b2b963be11e496 https://git.kernel.org/stable/c/44016a85419ca0d4f1e4d0127b330f8e4e2a57d0 https://git.kernel.org/stable/c/5595d30c4dc27d939635c3188c68203b6ece1711 https://git.kernel.org/stable/c/c3b821e8e406d5650e587b7ac624ac24e9b780a8
Powered by blists - more mailing lists