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 5D8133BD643 for ; Fri, 26 Jun 2026 19:43:10 +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=1782502991; cv=none; b=LWVZnBVdB9xgf8k16LvqapSMdwU8ZT6fe2iubb1c2GO9bZpCSeyoBTDWDaQ84JzcZ0OkBKDaifB18bkwi4PcWfXUE2s7sdWaUYIvi/z6DjT62JwT9GbMok9a94fKiyNoiqozmBzJEKX8MAtQ8gIlH6Y8OFEAF8E1lyClmi7Rfqw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1782502991; c=relaxed/simple; bh=zFWgmHO3cYvH5s5k5oHqrqy6E6BYOqWUwH7tnxC/cg8=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=VfMgwFVtNCRF7tKrMcrMaH5yjD+5lUyRBrX43nTAaTcgg4yrkLFW/YGkIKwCtALRoI+0rz+RZsv24kp6vNE5tbW97cUEtOXuSozliAZekGsEYIExcazNUkTCzy8iK+7gvR9fxC9BlFETkVPdYr8rMEex6UItQj1an7xbcfC2ur0= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=zYyUOMs4; 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="zYyUOMs4" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 51B0A1F000E9; Fri, 26 Jun 2026 19:43:09 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1782502989; bh=8xqY5Z8YkGGVEcyC280U5hipPjEhQAbUJjyh698uaas=; h=From:To:Cc:Subject:Date:Reply-To; b=zYyUOMs4NCA323g4740Q2LLiKZOffwqqJsMKwTkRNkz7iIL8iARD6LhcaOyeu8soN c4tOUWEvi5DO83H150FyqbuwadXkwfMh/U4sfo5kHblYEj569h6du6Aa9T07h5TVDI 8Xo4iNPyEUlsMTocF68JCqHpWZtN+/hSr1ai+r+0= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-53308: power: supply: max77705: Free allocated workqueue and fix removal order Date: Fri, 26 Jun 2026 20:40:41 +0100 Message-ID: <2026062620-CVE-2026-53308-8564@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=2875; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=NnnPY+RZrSLI+MLG3nraLK3c/R/5iijGjahVYVF5Cuk=; b=owGbwMvMwCRo6H6F97bub03G02pJDFl2V5eEPnoVtpzD/eybJQnzax9F6M2x2/z8uMSnzZ/rE nj8Jhz71BHLwiDIxCArpsjyZRvP0f0VhxS9DG1Pw8xhZQIZwsDFKQATydRkmF+3hitlzbXGrrti poIvFv+1KrFemMEwP11ETFtS5L+cklr2mrcrQkXvt6c/AAA= 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: max77705: Free allocated workqueue and fix removal order Use devm interface for allocating workqueue to fix two bugs at the same time: 1. Driver leaks the memory on remove(), because the workqueue is not destroyed. 2. Driver allocates workqueue and then registers interrupt handlers with devm interface. This means that probe error paths will not use a reversed order, but first destroy the workqueue and then, via devm release handlers, free the interrupt. The interrupt handler schedules work on this exact workqueue, thus if interrupt is hit in this short time window - after destroying workqueue, but before devm() frees the interrupt - the schedulled work will lead to use of freed memory. Change is not equivalent in the workqueue itself: use non-legacy API which does not set (__WQ_LEGACY | WQ_MEM_RECLAIM). The workqueue is used to update power supply (power_supply_changed()) status, thus there is no point to run it for memory reclaim. Note that dev_name() is not directly used in second argument to prevent possible unlikely parsing any "%" character in device name as format. The Linux kernel CVE team has assigned CVE-2026-53308 to this issue. Affected and fixed versions =========================== Issue introduced in 6.15 with commit a6a494c8e3ce1fe84aac538b087a4cab868ed83f and fixed in 7.0.10 with commit b98e4e57e34d099a8f846fa54749654082975ea0 Issue introduced in 6.15 with commit a6a494c8e3ce1fe84aac538b087a4cab868ed83f and fixed in 7.1 with commit 1e668baadefb16e81269dbfebf3ffc2672e3a3bb 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-53308 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/max77705_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/b98e4e57e34d099a8f846fa54749654082975ea0 https://git.kernel.org/stable/c/1e668baadefb16e81269dbfebf3ffc2672e3a3bb