CVE-2026-43316

published 8 May 2026 · updated 13 Nov 2026

media: solo6x10: Check for out of bounds chip_id

5.5MediumCVSS 5.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 5.10.252, Kernel 5.15.202, Kernel 6.1.165 and 12 more.

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]

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=2.6.36 <5.10.252, >=5.11 <5.15.202, >=5.16 <6.1.165, >=6.13 <6.18.16, >=6.19 <6.19.6, >=6.2 <6.6.128, >=6.7 <6.12.75, =7.0, >=faa4fd2a09517b39cc1f5d622453f97a59acfdac <0fdf6323c35a134f206dcad5babb4ff488552076, >=faa4fd2a09517b39cc1f5d622453f97a59acfdac <33af366211ee78e3b074ff44a16121e537e86826, >=faa4fd2a09517b39cc1f5d622453f97a59acfdac <4d6db0c6bbbfd8d7bbdbf7ab6a9c003752abf116, >=faa4fd2a09517b39cc1f5d622453f97a59acfdac <5849ae68d7b8b6ad55cc1bf0d227dd2ae6362528, >=faa4fd2a09517b39cc1f5d622453f97a59acfdac <603e3859393ee2ce91393b7d05e6e56e4b66e5cd, >=faa4fd2a09517b39cc1f5d622453f97a59acfdac <c327192ca26670cf6e588c1eeda66cd2fa97630e, >=faa4fd2a09517b39cc1f5d622453f97a59acfdac <d29f33b2cf98e4901cd5457d1ee34062e808df73, =2.6.36, >=faa4fd2a09517b39cc1f5d622453f97a59acfdac <0b3dadada2417782a63ce32dae05bafe1c949e3f5.10.252, 5.15.202, 6.1.165, 6.18.16, 6.19.6, 6.6.128, 6.12.75, 0fdf6323c35a134f206dcad5babb4ff488552076, 33af366211ee78e3b074ff44a16121e537e86826, 4d6db0c6bbbfd8d7bbdbf7ab6a9c003752abf116, 5849ae68d7b8b6ad55cc1bf0d227dd2ae6362528, 603e3859393ee2ce91393b7d05e6e56e4b66e5cd, c327192ca26670cf6e588c1eeda66cd2fa97630e, d29f33b2cf98e4901cd5457d1ee34062e808df73, 0b3dadada2417782a63ce32dae05bafe1c949e3f
linux-kernel: Kernel>=2.6.36 <5.10.252, >=5.11.0 <5.15.202, >=5.16.0 <6.1.165, >=6.13.0 <6.18.16, >=6.19.0 <6.19.6, >=6.2.0 <6.6.128, >=6.7.0 <6.12.755.10.252, 5.15.202, 6.1.165, 6.18.16, 6.19.6, 6.6.128, 6.12.75

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-43316 severity on Zeptric[![CVE-2026-43316](https://zeptric.io/badge/cve/CVE-2026-43316.svg)](https://zeptric.io/cve/CVE-2026-43316)