CVE-2026-43316: media: solo6x10: Check for out of bounds chip_id
In the Linux kernel, the following vulnerability has been resolved:
media: solo6x10: Check for out of bounds chipid
Clang with CONFIGUBSANSHIFT=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 istw286x() 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 istw286x]
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2026-43316?
The severity of CVE-2026-43316 is considered to be moderate as it may lead to unexpected behavior in the Linux kernel.
How do I fix CVE-2026-43316?
To fix CVE-2026-43316, you should update to the latest patched version of the Linux kernel that addresses this vulnerability.
Which Linux kernel versions are affected by CVE-2026-43316?
CVE-2026-43316 affects multiple versions of the Linux kernel ranging from 2.6.36 to 7.0-rc7.
What does CVE-2026-43316 exploit?
CVE-2026-43316 exploits an out of bounds access related to the chip_id in the solo6x10 media device driver.
How can I determine if my system is impacted by CVE-2026-43316?
You can determine if your system is impacted by checking the kernel version against the affected versions listed for CVE-2026-43316.