CVE-2026-43316: media: solo6x10: Check for out of bounds chip_id

CVE-2026-43316: media: solo6x10: Check for out of bounds chip_id

[Greg Kroah-Hartman]

From: Greg Kroah-Hartman <gregkh@kernel.org>

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