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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025011150-CVE-2024-57792-0002@gregkh>
Date: Sat, 11 Jan 2025 13:39: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-2024-57792: power: supply: gpio-charger: Fix set charge current limits

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ