CVE-2026-43316

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-05-08. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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]

CVSS v3
5.5
EG Score
5.5(medium)
EPSS
2.4%
KEV
Not listed

Published

May 8, 2026

Last Modified

May 15, 2026

Advisory Details (8)

Auto-updated Jun 17, 2026
No patch confirmed yet.
generic

media: solo6x10: Check for out of bounds chip_id - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d29f33b2cf98e4901cd5457d1ee34062e808df73
generic

media: solo6x10: Check for out of bounds chip_id - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c327192ca26670cf6e588c1eeda66cd2fa97630e
generic

media: solo6x10: Check for out of bounds chip_id - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/603e3859393ee2ce91393b7d05e6e56e4b66e5cd
generic

media: solo6x10: Check for out of bounds chip_id - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5849ae68d7b8b6ad55cc1bf0d227dd2ae6362528
generic

media: solo6x10: Check for out of bounds chip_id - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4d6db0c6bbbfd8d7bbdbf7ab6a9c003752abf116
generic

media: solo6x10: Check for out of bounds chip_id - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/33af366211ee78e3b074ff44a16121e537e86826
generic

media: solo6x10: Check for out of bounds chip_id - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0fdf6323c35a134f206dcad5babb4ff488552076
generic

media: solo6x10: Check for out of bounds chip_id - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0b3dadada2417782a63ce32dae05bafe1c949e3f

Vendor Advisories for CVE-2026-43316(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 7× in last 7d / 39× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 111 total refreshes for this CVE.

  1. 2026-07-15 16:57 UTCEPSS rescore
  2. 2026-07-15 02:00 UTCEPSS rescore
  3. 2026-07-13 22:30 UTCEPSS rescore
  4. 2026-07-13 06:13 UTCEPSS rescore
  5. 2026-07-12 05:46 UTCEPSS rescore
  6. 2026-07-11 08:27 UTCEPSS rescore
  7. 2026-07-09 19:10 UTCEPSS rescore
  8. 2026-07-08 15:16 UTCEPSS rescore
  9. 2026-07-07 13:46 UTCEPSS rescore
  10. 2026-07-06 16:27 UTCEPSS rescore
  11. 2026-07-06 02:23 UTCEPSS rescore
  12. 2026-07-05 02:30 UTCEPSS rescore
  13. 2026-07-04 06:31 UTCEPSS rescore
  14. 2026-07-01 15:06 UTCEPSS rescore
  15. 2026-06-30 23:22 UTCEPSS rescore
  16. 2026-06-29 14:06 UTCEPSS rescore
  17. 2026-06-28 14:07 UTCEPSS rescore
  18. 2026-06-28 05:09 UTCEG score recompute
  19. 2026-06-28 05:09 UTCGHSA enrichment
  20. 2026-06-28 04:56 UTCEPSS rescore
  21. 2026-06-27 03:08 UTCEPSS rescore
  22. 2026-06-26 21:35 UTCEG score recompute
  23. 2026-06-26 21:35 UTCGHSA enrichment
  24. 2026-06-25 13:49 UTCEPSS rescore
  25. 2026-06-25 13:49 UTCEPSS rescore
Show 75 more
  1. 2026-06-24 14:05 UTCEPSS rescore
  2. 2026-06-23 21:33 UTCEPSS rescore
  3. 2026-06-22 14:25 UTCEPSS rescore
  4. 2026-06-22 14:25 UTCEPSS rescore
  5. 2026-06-21 14:56 UTCEPSS rescore
  6. 2026-06-21 14:56 UTCEPSS rescore
  7. 2026-06-21 01:59 UTCEPSS rescore
  8. 2026-06-19 19:25 UTCEPSS rescore
  9. 2026-06-18 17:52 UTCEPSS rescore
  10. 2026-06-18 17:52 UTCEPSS rescore
  11. 2026-06-17 17:53 UTCEPSS rescore
  12. 2026-06-17 02:00 UTCEG score recompute
  13. 2026-06-17 02:00 UTCGHSA enrichment
  14. 2026-06-16 17:52 UTCEPSS rescore
  15. 2026-06-15 17:49 UTCEPSS rescore
  16. 2026-06-15 02:23 UTCEG score recompute
  17. 2026-06-15 02:23 UTCGHSA enrichment
  18. 2026-06-14 02:59 UTCEG score recompute
  19. 2026-06-14 02:59 UTCGHSA enrichment
  20. 2026-06-13 23:00 UTCEPSS rescore
  21. 2026-06-13 00:35 UTCEG score recompute
  22. 2026-06-13 00:35 UTCGHSA enrichment
  23. 2026-06-12 23:12 UTCEPSS rescore
  24. 2026-06-12 23:12 UTCEPSS rescore
  25. 2026-06-12 01:12 UTCEG score recompute
  26. 2026-06-12 01:12 UTCGHSA enrichment
  27. 2026-06-11 14:00 UTCEPSS rescore
  28. 2026-06-11 01:49 UTCEG score recompute
  29. 2026-06-11 01:49 UTCGHSA enrichment
  30. 2026-06-10 22:18 UTCEPSS rescore
  31. 2026-06-10 13:22 UTCEPSS rescore
  32. 2026-06-10 13:22 UTCEPSS rescore
  33. 2026-06-10 02:27 UTCEG score recompute
  34. 2026-06-10 02:27 UTCGHSA enrichment
  35. 2026-06-09 03:05 UTCEG score recompute
  36. 2026-06-09 03:05 UTCGHSA enrichment
  37. 2026-06-08 14:17 UTCEPSS rescore
  38. 2026-06-08 14:17 UTCEPSS rescore
  39. 2026-06-08 03:42 UTCEG score recompute
  40. 2026-06-08 03:42 UTCGHSA enrichment
  41. 2026-06-07 15:25 UTCEPSS rescore
  42. 2026-06-07 15:25 UTCEPSS rescore
  43. 2026-06-07 04:20 UTCEG score recompute
  44. 2026-06-07 04:20 UTCGHSA enrichment
  45. 2026-06-07 04:20 UTCEG score recompute
  46. 2026-06-07 04:20 UTCGHSA enrichment
  47. 2026-06-06 13:47 UTCEPSS rescore
  48. 2026-06-06 13:47 UTCEPSS rescore
  49. 2026-06-06 04:56 UTCEG score recompute
  50. 2026-06-06 04:56 UTCGHSA enrichment
  51. 2026-06-05 22:47 UTCEPSS rescore
  52. 2026-06-05 06:10 UTCEPSS rescore
  53. 2026-06-05 06:10 UTCEPSS rescore
  54. 2026-06-05 05:34 UTCEG score recompute
  55. 2026-06-05 05:34 UTCGHSA enrichment
  56. 2026-06-04 13:12 UTCEPSS rescore
  57. 2026-06-04 13:12 UTCEPSS rescore
  58. 2026-06-04 06:12 UTCEG score recompute
  59. 2026-06-04 06:12 UTCGHSA enrichment
  60. 2026-06-03 06:49 UTCEG score recompute
  61. 2026-06-03 06:49 UTCGHSA enrichment
  62. 2026-06-02 20:13 UTCEPSS rescore
  63. 2026-06-02 07:27 UTCEG score recompute
  64. 2026-06-02 07:27 UTCGHSA enrichment
  65. 2026-06-01 13:52 UTCEPSS rescore
  66. 2026-06-01 13:52 UTCEPSS rescore
  67. 2026-06-01 08:04 UTCEG score recompute
  68. 2026-06-01 08:04 UTCGHSA enrichment
  69. 2026-05-31 22:30 UTCEPSS rescore
  70. 2026-05-31 22:30 UTCEPSS rescore
  71. 2026-05-31 00:16 UTCEPSS rescore
  72. 2026-05-31 00:16 UTCEPSS rescore
  73. 2026-05-29 13:44 UTCEPSS rescore
  74. 2026-05-29 13:44 UTCEPSS rescore
  75. 2026-05-28 13:44 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-43316?
CVE-2026-43316 is a medium vulnerability published on May 8, 2026. In the Linux kernel, the following vulnerability has been resolved: media: solo6x10: Check for out of bounds chip_id Clang with CONFIGUBSANSHIFT=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…
When was CVE-2026-43316 disclosed?
CVE-2026-43316 was first published in the National Vulnerability Database on May 8, 2026, with the most recent update on May 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43316 actively exploited?
CVE-2026-43316 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-43316?
CVE-2026-43316 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-43316?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43316, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-43316

Explore →

Is Your Infrastructure Affected by CVE-2026-43316?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs