From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=100.103.45.18 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1793187578; b=CIqt+hu14OFhUOq2UEY5oX/7SF+zIGScmd+dETRee4JmzGzdjw8OT/JBW/0HuGSThkFs 35U4ny3vZXuRM2r4hT8VB+gtxj77t2oKsnYWb60nxJE2TnJrcEZlOsBVYjAFAc2cVDMYy Jx62jPjE0y3b8jllwIy8lBDmyqYdJB9/isoB1VBnM2C+5OaxT3ZwUNvWoGpQpYQBZIFZn 8NBJLp+MMroKi9PUzRTd/IwokzEBfIpiAiHskv03YK4feEM8WD2H76zqYETrfUoecDxyC XOJDQaU0TKb/MpDJMMuiQYZpm2BORgOyJ07lhgFHJqIG9XEkZUmk5wtW37s750F1taw== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1793187578; h=Received:DKIM-Signature:From:To:Cc:Subject:Date:Message-ID:X-Mailer: Reply-To:MIME-Version:Lines:X-Developer-Signature:X-Developer-Key: Content-Transfer-Encoding; bh=/7RsAzQMcR1r7ZYYRiFRvaClvybBdgYrpyBvZ/2oXsA=; b=l5Fa475CKK611np+fXGCNiaDi9M/y0NGDMqzdrMeTBSFgvNqlPYzSa7UjSfv4pIfy1n0 t6zhc7uSJMVj/9cTadV1ONvbrM6VaVB/nqq6sMjbjVjHJjvfqsYnpLwiDIsCL6S8qdJIs jElySsg5CgznKrtMo9So4MZDNFCYahtdbF9HzNFRF93MWpdF2u2wnCE8rEuBYsK5CirLb Bg4jBSgWef39tQWuVzq8usRLFz4dEv1MccqzBYAFZAumWc7uUnzCO2HEvDmVefvQxPebo dOc7dghX2Z5dqg2OeDoumtwuKpSlQLx8AF4E91XQigxM2YjzuMkO1cWYL+g4bWyxtXQ== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=Zp1MlTUF; arc=none smtp.remote-ip=100.103.45.18 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id E13C7606A31C for ; Wed, 28 Oct 2026 11:39:37 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key, unprotected) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=Zp1MlTUF Received: by smtp.kernel.org (Postfix) with ESMTPSA id 1D3841F01825; Wed, 28 Oct 2026 11:39:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1793187577; bh=/7RsAzQMcR1r7ZYYRiFRvaClvybBdgYrpyBvZ/2oXsA=; h=From:To:Cc:Subject:Date:Reply-To; b=Zp1MlTUFrHrtn4YTrYFB5/4wjhA8Pq14V6asDMW/u3eDTGccUhVxfOkjDmC+QdxPJ yhBGyLYFmgy01ggUBuf1DiAe09a0bouKMm+P93cwVqUD5fCVrxJ4h+rDwGjyEUd2mJ mVZH6pibqNwDxc+GVp3GQUBPNmvKWWEn7WAg7QAE= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-99161: i2c: viai2c-wmt: Fix clock leak in wmt_i2c_probe() Date: Wed, 28 Oct 2026 11:35:48 +0100 Message-ID: <2026102805-CVE-2026-99161-e087@gregkh> X-Mailer: git-send-email 2.56.0 Reply-To: , X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=2302; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=Eov9NSIcTz64tVjaIu+FkKDaqsGOy2T8OYfyDwomfNU=; b=owGbwMvMwCRo6H6F97bub03G02pJDFkPz988skVFQOiLWuD8RttLn4872y7IemYi/455pjrvp 0D+TE3bjlgWBkEmBlkxRZYv23iO7q84pOhlaHsaZg4rE8gQBi5OAZhIcj7DgmPBt951tpt+ZVyd EB+y5Kv4tBtKAgwLJv99/Fh5hvm2NbPLzf65KLKec1gpDAA= 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: i2c: viai2c-wmt: Fix clock leak in wmt_i2c_probe() In wmt_i2c_probe(), i2c->clk is acquired using of_clk_get(). If any subsequent operation fails or when the module is unloaded, the clock reference count is never decremented via clk_put(), leading to a resource leak. Switch to devm_clk_get() so that the clock is automatically managed and released. The Linux kernel CVE team has assigned CVE-2026-99161 to this issue. Affected and fixed versions =========================== Issue introduced in 3.11 with commit 560746eb79d3124a278452c8dd968682b521cc82 and fixed in 6.18.59 with commit 5d476bb76b7d72d8b7ed04a9c614900b097e3af7 Issue introduced in 3.11 with commit 560746eb79d3124a278452c8dd968682b521cc82 and fixed in 7.2.13 with commit 1875de656370c89b99a150d220df876288ee0344 Issue introduced in 3.11 with commit 560746eb79d3124a278452c8dd968682b521cc82 and fixed in 7.3 with commit aaabefc79b0ff0018e8e3832169bbe359d0551fc 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-99161 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/i2c/busses/i2c-viai2c-wmt.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/5d476bb76b7d72d8b7ed04a9c614900b097e3af7 https://git.kernel.org/stable/c/1875de656370c89b99a150d220df876288ee0344 https://git.kernel.org/stable/c/aaabefc79b0ff0018e8e3832169bbe359d0551fc