CVE-2026-43316media: solo6x10: Check for out of bounds chip_id
- 5.5MediumCVSS base score
- 0.12%Exploitation in 30 daysEPSS · top 98% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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]
Timeline
ID reserved
By Linux
- 7 days later
· 7 days later
Published
- 3 days later
· 3 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.12% · top 98% of all CVEs (14 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected faa4fd2a09517b39cc1f5d622453f97a59acfdac – < c327192ca26670cf6e588c1eeda66cd2fa97630e
- affected faa4fd2a09517b39cc1f5d622453f97a59acfdac – < 0b3dadada2417782a63ce32dae05bafe1c949e3f
- affected faa4fd2a09517b39cc1f5d622453f97a59acfdac – < 603e3859393ee2ce91393b7d05e6e56e4b66e5cd
- affected faa4fd2a09517b39cc1f5d622453f97a59acfdac – < 33af366211ee78e3b074ff44a16121e537e86826
- affected faa4fd2a09517b39cc1f5d622453f97a59acfdac – < 5849ae68d7b8b6ad55cc1bf0d227dd2ae6362528
- affected faa4fd2a09517b39cc1f5d622453f97a59acfdac – < d29f33b2cf98e4901cd5457d1ee34062e808df73
- affected faa4fd2a09517b39cc1f5d622453f97a59acfdac – < 4d6db0c6bbbfd8d7bbdbf7ab6a9c003752abf116
- affected faa4fd2a09517b39cc1f5d622453f97a59acfdac – < 0fdf6323c35a134f206dcad5babb4ff488552076
- affected 2.6.36
- unaffected < 2.6.36
- unaffected 5.10.252 – ≤ 5.10.*
- unaffected 5.15.202 – ≤ 5.15.*
- unaffected 6.1.165 – ≤ 6.1.*
- unaffected 6.6.128 – ≤ 6.6.*
- unaffected 6.12.75 – ≤ 6.12.*
- unaffected 6.18.16 – ≤ 6.18.*
- unaffected 6.19.6 – ≤ 6.19.*
- unaffected 7.0 – ≤ *
References
References8
- https://git.kernel.org/stable/c/c327192ca26670cf6e588c1eeda66cd2fa97630e (opens in a new tab)
- https://git.kernel.org/stable/c/0b3dadada2417782a63ce32dae05bafe1c949e3f (opens in a new tab)
- https://git.kernel.org/stable/c/603e3859393ee2ce91393b7d05e6e56e4b66e5cd (opens in a new tab)
- https://git.kernel.org/stable/c/33af366211ee78e3b074ff44a16121e537e86826 (opens in a new tab)
- https://git.kernel.org/stable/c/5849ae68d7b8b6ad55cc1bf0d227dd2ae6362528 (opens in a new tab)
- https://git.kernel.org/stable/c/d29f33b2cf98e4901cd5457d1ee34062e808df73 (opens in a new tab)
- https://git.kernel.org/stable/c/4d6db0c6bbbfd8d7bbdbf7ab6a9c003752abf116 (opens in a new tab)
- https://git.kernel.org/stable/c/0fdf6323c35a134f206dcad5babb4ff488552076 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-28600 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-43316)Record last updated .