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

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **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:** Yes
- **Published:** 8 May 2026
- **Updated:** 11 May 2026
- **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, UBUNTU-CVE-2026-43316

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

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-43316 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-43316 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-43316/ (Markdown: https://insights.sbomify.com/CVE-2026-43316/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-43316
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-43316
- OSV: https://osv.dev/vulnerability/CVE-2026-43316

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-43316/
Summaries are generated and may contain mistakes; the official description above is the record.