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 930E6287510 for ; Fri, 8 May 2026 13:26:23 +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=1778246783; cv=none; b=nB9KCMWojX525dg8RTE1S7Vm2tnVcFZxqKhR0yCPlrjmUMPmvob6wpqJgxqk2LgEZzmybNETDnElpLyXZhnDz1G8wiAKtXvTY2VRJlxiAGfYPkKPSzLFBZZmD5C76/diKwbmEVBn9OedvwPnugZF/wjlrtKZvaiUNpq7RiIAmNM= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1778246783; c=relaxed/simple; bh=MmkFruaK/nektKNVlX7j/ZsjTEJNMr6VlDtJ1DcGoSI=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=OMxcOsWdEg3PUwWBEE/WM6QUvxy8kbGx5TCY0j3McmRgxJzEH3P7phD+vgTWizclU+2DF4YTAYLoO7DV/+Lm45Cujnm8EAtreq+S7MUX6SEl189misnEJgbJPCwKhBq05yMMWweCg7icCK7p7rMJHMmWeYfaLMm34zO/6vHZ97k= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=B4vboaOq; 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="B4vboaOq" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 8B4CDC2BCB0; Fri, 8 May 2026 13:26:22 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1778246783; bh=MmkFruaK/nektKNVlX7j/ZsjTEJNMr6VlDtJ1DcGoSI=; h=From:To:Cc:Subject:Date:Reply-To:From; b=B4vboaOqRr7nKuGpaZLyD4XB3mGYCrSaGLLANEG8sAkQhL3UzNHzaGuK42SazHZ2H me6jDQmGiZub1pH526Zbew4f4G9u1R61BssKfVrdHncFJXchYVva0Gwp7yuUhBp9V1 2FjjvWj7BJik8A17RrwXDPUYEJOc9IqT2Y579ILA= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-43316: media: solo6x10: Check for out of bounds chip_id Date: Fri, 8 May 2026 15:26:19 +0200 Message-ID: <2026050817-CVE-2026-43316-39a4@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=3263; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=YKj9MSJBxcpEDzEv/I4+kZCIqyifm96h5vdlnLDQDYg=; b=owGbwMvMwCRo6H6F97bub03G02pJDJl/n1Sdnsj7alGjc5zVthax1E/26rILsv9O5fJvaVL+s FRw5oM5HbEsDIJMDLJiiixftvEc3V9xSNHL0PY0zBxWJpAhDFycAjCRI+sZFkwz3X+wWIOzZllz 4SORpZIRMctlPzEsmNvJ8+Ug24PsB4VfZPzrL3p4nP43FwA= 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: media: solo6x10: Check for out of bounds chip_id Clang with CONFIG_UBSAN_SHIFT=y noticed a condition where a signed type (literal "1" is an "int") could end up being shifted beyond 32 bits, so instrumentation was added (and due to the double is_tw286x() call seen via inlining), Clang decides the second one must now be undefined behavior and elides the rest of the function[1]. This is a known problem with Clang (that is still being worked on), but we can avoid the entire problem by actually checking the existing max chip ID, and now there is no runtime instrumentation added at all since everything is known to be within bounds. Additionally use an unsigned value for the shift to remove the instrumentation even without the explicit bounds checking. [hverkuil: fix checkpatch warning for is_tw286x] The Linux kernel CVE team has assigned CVE-2026-43316 to this issue. Affected and fixed versions =========================== Fixed in 5.10.252 with commit c327192ca26670cf6e588c1eeda66cd2fa97630e Fixed in 5.15.202 with commit 0b3dadada2417782a63ce32dae05bafe1c949e3f Fixed in 6.1.165 with commit 603e3859393ee2ce91393b7d05e6e56e4b66e5cd Fixed in 6.6.128 with commit 33af366211ee78e3b074ff44a16121e537e86826 Fixed in 6.12.75 with commit 5849ae68d7b8b6ad55cc1bf0d227dd2ae6362528 Fixed in 6.18.16 with commit d29f33b2cf98e4901cd5457d1ee34062e808df73 Fixed in 6.19.6 with commit 4d6db0c6bbbfd8d7bbdbf7ab6a9c003752abf116 Fixed in 7.0 with commit 0fdf6323c35a134f206dcad5babb4ff488552076 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-43316 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/media/pci/solo6x10/solo6x10-tw28.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/c327192ca26670cf6e588c1eeda66cd2fa97630e https://git.kernel.org/stable/c/0b3dadada2417782a63ce32dae05bafe1c949e3f https://git.kernel.org/stable/c/603e3859393ee2ce91393b7d05e6e56e4b66e5cd https://git.kernel.org/stable/c/33af366211ee78e3b074ff44a16121e537e86826 https://git.kernel.org/stable/c/5849ae68d7b8b6ad55cc1bf0d227dd2ae6362528 https://git.kernel.org/stable/c/d29f33b2cf98e4901cd5457d1ee34062e808df73 https://git.kernel.org/stable/c/4d6db0c6bbbfd8d7bbdbf7ab6a9c003752abf116 https://git.kernel.org/stable/c/0fdf6323c35a134f206dcad5babb4ff488552076