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 DD77726460A for ; Tue, 8 Apr 2025 08:18:17 +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=1744100300; cv=none; b=nF33fPBAcbAd3gf6GLh/ZxwezBcMCjha9FfGLn6E/vxWCmbdBqETBtpZdgT/ckFZm/xCLnXB0/PbYvm9yFapC/hzlpy8gkqyPfQKiqX56RFwLA/jjNwNrtlYSEOlsVC3P2cZbVQXBnWeRxTtAAnv2Iq8CYlRBLJvmB0RoXatzis= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1744100300; c=relaxed/simple; bh=BI96H/cWAKJJFETPrQXytmqhmubTeGZ19I6qaw4JoNg=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=Kl3N6txXjvFwy7M7Y0d4DND1+PqJAVawuPhXNKkEyqbKDz2NxN2eTbfk8LGt+3LooFHDXXIun7DNkhCkiIPp4s228jv83q7D8bPrUzExrNAHpvc+8Ug2omxQ/xRT/6B7JTJ4qsjmraJVN/jiYKbUYStNYFyDtkgdvrJ9bPNlJZg= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=WU1dXJ3a; 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="WU1dXJ3a" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 004BEC4CEEB; Tue, 8 Apr 2025 08:18:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1744100297; bh=BI96H/cWAKJJFETPrQXytmqhmubTeGZ19I6qaw4JoNg=; h=From:To:Cc:Subject:Date:Reply-to:From; b=WU1dXJ3agNGotMk1sHsIOzZNZ+kXBihkT/yhPm5+5oJGAbJBY8LfU7RUSvyPWj2XX GXFiGFhqBjVX5uGvxvil9CZs9o0ScJp4Cb36x0cX0GSrjQZFvC5YWcGYAXtqV0/Amf Pmv1JThXsZ960SwQLYPoVrCQ6A1AdWoNsWwFVl48= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2025-22009: regulator: dummy: force synchronous probing Date: Tue, 8 Apr 2025 10:16:43 +0200 Message-ID: <2025040842-CVE-2025-22009-2b2b@gregkh> X-Mailer: git-send-email 2.49.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=3038; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=BI96H/cWAKJJFETPrQXytmqhmubTeGZ19I6qaw4JoNg=; b=owGbwMvMwCRo6H6F97bub03G02pJDOlfbmdfCfjbJ7InzOPOizU811KdQ9w0di8pYVTiq/txh Cl2+tHPHbEsDIJMDLJiiixftvEc3V9xSNHL0PY0zBxWJpAhDFycAjCRrBSGBau15nNFTTh4bcdZ If+IBuvGg7ekfzMsODBh6mINm5cuQafK9h2b5al3NGRDMgA= 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: regulator: dummy: force synchronous probing Sometimes I get a NULL pointer dereference at boot time in kobject_get() with the following call stack: anatop_regulator_probe() devm_regulator_register() regulator_register() regulator_resolve_supply() kobject_get() By placing some extra BUG_ON() statements I could verify that this is raised because probing of the 'dummy' regulator driver is not completed ('dummy_regulator_rdev' is still NULL). In the JTAG debugger I can see that dummy_regulator_probe() and anatop_regulator_probe() can be run by different kernel threads (kworker/u4:*). I haven't further investigated whether this can be changed or if there are other possibilities to force synchronization between these two probe routines. On the other hand I don't expect much boot time penalty by probing the 'dummy' regulator synchronously. The Linux kernel CVE team has assigned CVE-2025-22009 to this issue. Affected and fixed versions =========================== Issue introduced in 6.4 with commit 259b93b21a9ffe5117af4dfb5505437e463c6a5a and fixed in 6.6.85 with commit e26f24ca4fb940b15e092796c5993142a2558bd9 Issue introduced in 6.4 with commit 259b93b21a9ffe5117af4dfb5505437e463c6a5a and fixed in 6.12.21 with commit d3b83a1442a09b145006eb4294b1a963c5345c9c Issue introduced in 6.4 with commit 259b93b21a9ffe5117af4dfb5505437e463c6a5a and fixed in 6.13.9 with commit 5ade367b56c3947c990598df92395ce737bee872 Issue introduced in 6.4 with commit 259b93b21a9ffe5117af4dfb5505437e463c6a5a and fixed in 6.14 with commit 8619909b38eeebd3e60910158d7d68441fc954e9 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-2025-22009 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/regulator/dummy.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/e26f24ca4fb940b15e092796c5993142a2558bd9 https://git.kernel.org/stable/c/d3b83a1442a09b145006eb4294b1a963c5345c9c https://git.kernel.org/stable/c/5ade367b56c3947c990598df92395ce737bee872 https://git.kernel.org/stable/c/8619909b38eeebd3e60910158d7d68441fc954e9