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 65E72582BAF for ; Fri, 11 Sep 2026 19:51:56 +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=1789156327; cv=none; b=SRl48luIoc4Jqhi5+i1DEGQvWBEAPtZQXZPRS8K4Dg8skm4QhQBUHOUhNy1Fody3d1wnQx32tC3OJw9g/7MMN2A60uSipTerFa99XqvKHjcIMN5bd/ORDfT1UDsLBJdThs2TJcom5Z26NNt7gW3foNoDHD4cg2QSIppgWmVBtzo= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1789156327; c=relaxed/simple; bh=Hz1y2e4gtyVyw/qbyd2L///kZICQFEFP9Adz1nQ7MLA=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=FC5b39Kg0dCp7ZgEGbSbOClJltx4STcmz5WGZnkk3ETdKfuVYZ4wCmh9qSXPURS48Fs2kR1sJSk4uVKlKFG3K0gbT+y+LxwujhTkiFibClYH84zAA7NboZhkqEo5/j2FTSKzI3KV0hmOL33hGjODo1bbX9sV+fUZ8zpQ8RTpQIE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=dl9gEc44; 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="dl9gEc44" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 990041F00893; Fri, 11 Sep 2026 19:51:55 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1789156316; bh=z0+SuWoO+pMwnZ7yY+XNCzQVLcuAFC50rWQTSPP9YY8=; h=From:To:Cc:Subject:Date:Reply-To; b=dl9gEc44yMv0VZGwPq01B9P5h19jbjdFaodfeRmrOOo5MZah2w2t2AQ1lYdCKGI0r x75b/278+zs14Z1wP5Y2OvOZx+tztxuXGRNHrTseiGK/yFSJZjqJSKpZCjljaw7suq enmnaZMP2YBUFXHUHyQkNZtCFywFoRIuzC1SHB5k= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-89475: power: supply: bq24257: fix use-after-free on remove Date: Fri, 11 Sep 2026 21:42:44 +0200 Message-ID: <2026091104-CVE-2026-89475-5257@gregkh> X-Mailer: git-send-email 2.55.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=2927; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=JaXNjlIOqL5+dEreVpzCQxlcsjqhIsFATjUGT5KH+HA=; b=owGbwMvMwCRo6H6F97bub03G02pJDFlLIgNmqriFPX637TnL90eHbisEiIvJfmfJ15yd+z6d6 53F3H03OmJZGASZGGTFFFm+bOM5ur/ikKKXoe1pmDmsTCBDGLg4BWAi7+oY5of+b+z88OV2V/Wk zkv9DYmzV/YxajAsOClX6Zf8wCHSL/ZBvsX9D+GL9hu/BgA= 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: bq24257: fix use-after-free on remove The STAT-pin interrupt is devm-managed, so it stays armed until the devm cleanup that runs after remove() returns. remove() cancels bq->iilimit_setup_work while the threaded handler can still fire; that handler reschedules the work and dereferences bq, so the work runs against freed memory once devm frees bq. Make the delayed work device-managed with devm_delayed_work_autocancel(), registered before the interrupt request. The devm cleanup then releases the interrupt first, so the handler can no longer reschedule the work, and cancels the work before bq is freed. The explicit cancel_delayed_work_sync() in remove() is no longer needed and is dropped. Found by static analysis. The Linux kernel CVE team has assigned CVE-2026-89475 to this issue. Affected and fixed versions =========================== Issue introduced in 4.2 with commit 2219a935963e5eeb19e5abfb99475fcc06bbb804 and fixed in 6.12.109 with commit 861ec73ce86e2ca18082cc7be4f140a5bbdf1428 Issue introduced in 4.2 with commit 2219a935963e5eeb19e5abfb99475fcc06bbb804 and fixed in 6.18.50 with commit f495808cdd6d9576965787cf6d9737d0b0e86b73 Issue introduced in 4.2 with commit 2219a935963e5eeb19e5abfb99475fcc06bbb804 and fixed in 7.2.4 with commit 47ccbad210f48721c30d69d65b83dc9fff919ca9 Issue introduced in 4.2 with commit 2219a935963e5eeb19e5abfb99475fcc06bbb804 and fixed in 7.3-rc1 with commit 9d34c9d660c3d0931d2cc749c46c47cf31f96e48 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-89475 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/bq24257_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/861ec73ce86e2ca18082cc7be4f140a5bbdf1428 https://git.kernel.org/stable/c/f495808cdd6d9576965787cf6d9737d0b0e86b73 https://git.kernel.org/stable/c/47ccbad210f48721c30d69d65b83dc9fff919ca9 https://git.kernel.org/stable/c/9d34c9d660c3d0931d2cc749c46c47cf31f96e48