From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (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 921533E3D8D for ; Wed, 27 May 2026 12:22:50 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1779884571; cv=none; b=W/HRgxd11UiGrVT4nXfgiPx0LySvvxPoNGvh4EozeW0PNInFWUfFSizo/DRLyHgxCdrgn8UemwIouLK4fa7Oz7HIahO1a07GQYe9U5P8V162/LQ2Pck8Wa2zggYlt0MkKMv9nNbHFEWe0oBeC6lb3ZJq0059QsbPjFssogtkSbw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1779884571; c=relaxed/simple; bh=E3LMCRvxqADj+rNzzmPrCH51UG0tIj13tSjgi5vNILc=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=VGXxdXy2fidy2QVTGNt64duhoAcmVo4/K/z2w2jGKdn13A2Q0LiI7wR26WgbwSy+lp4+8WoJuyKM4sQNRuxMN8tnfofE3G5a94nKMSoS2cLe7WRB+QCoqX8CPDJ2biHGZJMIvcrC/01453AMg+OpjapKSpMizEMmfwPmp6IN0+M= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=vtXYPLfT; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="vtXYPLfT" Received: by smtp.kernel.org (Postfix) with ESMTPSA id ECB1C1F000E9; Wed, 27 May 2026 12:22:49 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1779884570; bh=Y1fNAi798sE+Nd7+xTGXzrpZM+67LPKbqTbnGI0My/I=; h=From:To:Cc:Subject:Date:Reply-To; b=vtXYPLfTyGi5pt49Cc1tNUB2uG4VlkXTNnRB3/thYXEPSHbG/4E7KDd8RqymeTpwW 9Bw3rh9nJ97DV98DsNqtCW9ZJgUUzZB6izClYlLMB14EMdcnM4CJTshPh1g7omu9+r +F7ZpaJ9efgdvsih9/HRO9GAPUmmxc+VRyUgYI+k= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-45902: power: supply: bq256xx: Fix use-after-free in power_supply_changed() Date: Wed, 27 May 2026 14:19:04 +0200 Message-ID: <2026052720-CVE-2026-45902-bfec@gregkh> X-Mailer: git-send-email 2.54.0 Reply-To: , Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=4066; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=dIESasIVxrtTSj1iNUfDLSuJbyx//LOPdUWVLku+rkM=; b=owGbwMvMwCRo6H6F97bub03G02pJDFliD3kunfw1LaJNn7VuUVuOPKO8evXCF1/2f3Y251fas 2GZ3K3KjlgWBkEmBlkxRZYv23iO7q84pOhlaHsaZg4rE8gQBi5OAZjIKhGGBUtEPU+7bWt4Z8H/ Vs+hKcjbU2lBA8OCaasYp7v0HfE+YhmyP7fq2MyyrUcFAA== X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit From: Greg Kroah-Hartman Description =========== In the Linux kernel, the following vulnerability has been resolved: power: supply: bq256xx: Fix use-after-free in power_supply_changed() Using the `devm_` variant for requesting IRQ _before_ the `devm_` variant for allocating/registering the `power_supply` handle, means that the `power_supply` handle will be deallocated/unregistered _before_ the interrupt handler (since `devm_` naturally deallocates in reverse allocation order). This means that during removal, there is a race condition where an interrupt can fire just _after_ the `power_supply` handle has been freed, *but* just _before_ the corresponding unregistration of the IRQ handler has run. This will lead to the IRQ handler calling `power_supply_changed()` with a freed `power_supply` handle. Which usually crashes the system or otherwise silently corrupts the memory... Note that there is a similar situation which can also happen during `probe()`; the possibility of an interrupt firing _before_ registering the `power_supply` handle. This would then lead to the nasty situation of using the `power_supply` handle *uninitialized* in `power_supply_changed()`. Fix this racy use-after-free by making sure the IRQ is requested _after_ the registration of the `power_supply` handle. The Linux kernel CVE team has assigned CVE-2026-45902 to this issue. Affected and fixed versions =========================== Issue introduced in 5.12 with commit 32e4978bb920d047fe5de3ea42d176f267c01f63 and fixed in 5.15.202 with commit 81d3688c9a2158329391e08f2d0b8ba204216044 Issue introduced in 5.12 with commit 32e4978bb920d047fe5de3ea42d176f267c01f63 and fixed in 6.1.165 with commit 74b5a88318db97d51bb40f774736553c2acd1514 Issue introduced in 5.12 with commit 32e4978bb920d047fe5de3ea42d176f267c01f63 and fixed in 6.6.128 with commit cb5c743936edcebc51880eeb6bf04979b5c9438b Issue introduced in 5.12 with commit 32e4978bb920d047fe5de3ea42d176f267c01f63 and fixed in 6.12.75 with commit 83c27fdd696ac13d023ef7a0345301be93209c53 Issue introduced in 5.12 with commit 32e4978bb920d047fe5de3ea42d176f267c01f63 and fixed in 6.18.14 with commit 4b6fb0b6124f558131e502e3ffd03e6583b3ace6 Issue introduced in 5.12 with commit 32e4978bb920d047fe5de3ea42d176f267c01f63 and fixed in 6.19.4 with commit 8796910131a32ff29275052df768ef022929a394 Issue introduced in 5.12 with commit 32e4978bb920d047fe5de3ea42d176f267c01f63 and fixed in 7.0 with commit 8005843369723d9c8975b7c4202d1b85d6125302 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-2026-45902 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/bq256xx_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/81d3688c9a2158329391e08f2d0b8ba204216044 https://git.kernel.org/stable/c/74b5a88318db97d51bb40f774736553c2acd1514 https://git.kernel.org/stable/c/cb5c743936edcebc51880eeb6bf04979b5c9438b https://git.kernel.org/stable/c/83c27fdd696ac13d023ef7a0345301be93209c53 https://git.kernel.org/stable/c/4b6fb0b6124f558131e502e3ffd03e6583b3ace6 https://git.kernel.org/stable/c/8796910131a32ff29275052df768ef022929a394 https://git.kernel.org/stable/c/8005843369723d9c8975b7c4202d1b85d6125302