From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id F173F199EB7 for ; Sat, 11 Jan 2025 12:40:00 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1736599201; cv=none; b=XfcMz74p+bpjUw+uUBk/H6qHiUo61VDCrpALjlmQ84TOcr+WTm5rsZrpv893q5vbSP28BWGAYYCklsK046aa4QsVGStfRBgOD40i7Fy2HwdcsElnrmBkrz+jNRcGGjtHwt50QUnbmey6AQBFI/5xGHKjNluS9g36dSklxaqJe6g= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1736599201; c=relaxed/simple; bh=OEMJAr7/CeA7nXt4oPbVSsgIKdJE0iN7oYIywMsyXw0=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=Pu2b0eP3mjEFrn5AI0ekSR8Pg58iz5lAnOe+hmbc3yspbHNbMZXPkQkkhGFS/Ipff/oAHHurWtXtMO69HsZh7IJxUCYrk3L0iM+PRuohWFvycWxn7f6uiEmEL/rfupfFU+MuwVZOioSoQLA0Zy8QqvqB1QG7qp9/i+14S7XvUOg= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=Jvnwtxw/; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="Jvnwtxw/" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 5EA76C4CED2; Sat, 11 Jan 2025 12:40:00 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1736599200; bh=OEMJAr7/CeA7nXt4oPbVSsgIKdJE0iN7oYIywMsyXw0=; h=From:To:Cc:Subject:Date:Reply-to:From; b=Jvnwtxw/x1IGLpBtYNvz2EFiBYl34wVBpR/K0c9rVqv7d+GYJSbdDQT60xYMaCDpB wS2XjySJIPTYElI360Vt5AJgq7qsTbQ3p41XT4n1Og5xpXm4q1UNEjV8jQx+dmk0tQ cmMLs0KnBR8bJEgP5dvdiPRRRtlIdFfpwlGxrdCA= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2024-57792: power: supply: gpio-charger: Fix set charge current limits Date: Sat, 11 Jan 2025 13:39:51 +0100 Message-ID: <2025011150-CVE-2024-57792-0002@gregkh> X-Mailer: git-send-email 2.48.0 Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Reply-to: , X-Developer-Signature: v=1; a=openpgp-sha256; l=2967; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=OEMJAr7/CeA7nXt4oPbVSsgIKdJE0iN7oYIywMsyXw0=; b=owGbwMvMwCRo6H6F97bub03G02pJDOlNadMOv5r3sPsVR9gvzpTbMZvnV7YVrSvKXlGtNbVXu XrlLN8tHbEsDIJMDLJiiixftvEc3V9xSNHL0PY0zBxWJpAhDFycAjCR4isM80wnXQwxsMqRlQrd 5a50k73zfVKeJMP8stTVLO8PHexQinq9+vjJF8/n2TyTAQA= X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit Description =========== In the Linux kernel, the following vulnerability has been resolved: power: supply: gpio-charger: Fix set charge current limits Fix set charge current limits for devices which allow to set the lowest charge current limit to be greater zero. If requested charge current limit is below lowest limit, the index equals current_limit_map_size which leads to accessing memory beyond allocated memory. The Linux kernel CVE team has assigned CVE-2024-57792 to this issue. Affected and fixed versions =========================== Issue introduced in 5.10 with commit be2919d8355e4651386ad2fb61ddb6efe4533b1b and fixed in 5.10.233 with commit b29c7783ac1fe36d639c089cf471ac7a46df05f0 Issue introduced in 5.10 with commit be2919d8355e4651386ad2fb61ddb6efe4533b1b and fixed in 5.15.176 with commit c3703d9340ca2820e1ac63256f4b423ea8559831 Issue introduced in 5.10 with commit be2919d8355e4651386ad2fb61ddb6efe4533b1b and fixed in 6.1.123 with commit 6abbbd8286b6f944eecf3c74444c138590135211 Issue introduced in 5.10 with commit be2919d8355e4651386ad2fb61ddb6efe4533b1b and fixed in 6.6.69 with commit 13eb3cae1d8e23cce96c095abe34da8028c09ac5 Issue introduced in 5.10 with commit be2919d8355e4651386ad2fb61ddb6efe4533b1b and fixed in 6.12.8 with commit f6279a98db132da0cfff18712a1b06478c32007f Issue introduced in 5.10 with commit be2919d8355e4651386ad2fb61ddb6efe4533b1b and fixed in 6.13-rc5 with commit afc6e39e824ad0e44b2af50a97885caec8d213d1 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-57792 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/power/supply/gpio-charger.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/b29c7783ac1fe36d639c089cf471ac7a46df05f0 https://git.kernel.org/stable/c/c3703d9340ca2820e1ac63256f4b423ea8559831 https://git.kernel.org/stable/c/6abbbd8286b6f944eecf3c74444c138590135211 https://git.kernel.org/stable/c/13eb3cae1d8e23cce96c095abe34da8028c09ac5 https://git.kernel.org/stable/c/f6279a98db132da0cfff18712a1b06478c32007f https://git.kernel.org/stable/c/afc6e39e824ad0e44b2af50a97885caec8d213d1