CVE-2026-43316 media: solo6x10: Check for out of bounds chip_id
A missing bounds check on chip_id in the solo6x10 media driver can cause undefined behavior and potential crashes due to integer overflow issues.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-43316?
CVE-2026-43316 is a medium-severity vulnerability in Linux kernel, published on 8 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Official 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]
Which versions are affected by CVE-2026-43316?
It affects 1 product.
Products include Linux kernel.
How do I fix CVE-2026-43316?
Apply the vendor's patch.
Is CVE-2026-43316 being exploited?
There is no known exploitation of CVE-2026-43316 in the wild and no public exploit code.
Other vulnerabilities in Linux kernel
Sources
Also known as BELL-CVE-2026-43316, DEBIAN-CVE-2026-43316, GHSA-xw5q-w7ff-jgm4, ROOT-OS-DEBIAN-11-CVE-2026-43316, ROOT-OS-UBUNTU-2204-CVE-2026-43316, ROOT-OS-UBUNTU-2404-CVE-2026-43316 and 1 more.