CVE-2026-45956

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-27. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: 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:

drm/exynos: vidi: use priv->vidi_dev for ctx lookup in vidi_connection_ioctl()

vidi_connection_ioctl() retrieves the driver_data from drm_dev->dev to obtain a struct vidi_context pointer. However, drm_dev->dev is the exynos-drm master device, and the driver_data contained therein is not the vidi component device, but a completely different device.

This can lead to various bugs, ranging from null pointer dereferences and garbage value accesses to, in unlucky cases, out-of-bounds errors, use-after-free errors, and more.

To resolve this issue, we need to store/delete the vidi device pointer in exynos_drm_private->vidi_dev during bind/unbind, and then read this exynos_drm_private->vidi_dev within ioctl() to obtain the correct struct vidi_context pointer.

CVSS v3
7.8
EG Score
7.8(medium)
EPSS
2.6%
KEV
Not listed

Published

May 27, 2026

Last Modified

June 16, 2026

Advisory Details (7)

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

drm/exynos: vidi: use priv->vidi_dev for ctx lookup in vidi_connection_ioctl() - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/exynos: vidi: use priv->vidi_dev for ctx lookup in vidi_connection_ioctl() - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/exynos: vidi: use priv->vidi_dev for ctx lookup in vidi_connection_ioctl() - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/exynos: vidi: use priv->vidi_dev for ctx lookup in vidi_connection_ioctl() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/875fa28690e93ed5296c31d3344556c6bb867234
generic

drm/exynos: vidi: use priv->vidi_dev for ctx lookup in vidi_connection_ioctl() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/65d1213baffa363f2eb1117b1dc7acc573b890f8
generic

drm/exynos: vidi: use priv->vidi_dev for ctx lookup in vidi_connection_ioctl() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2987642c5213508c6c9e718324c0d5289a92c474
generic

drm/exynos: vidi: use priv->vidi_dev for ctx lookup in vidi_connection_ioctl() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/21ca24ba51a2c28bcc4df9d7e5a40b0eb66ab76d

Vendor Advisories for CVE-2026-45956(2)

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

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-45956?
CVE-2026-45956 is a high vulnerability published on May 27, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/exynos: vidi: use priv->vididev for ctx lookup in vidiconnection_ioctl() vidiconnectionioctl() retrieves the driverdata from drmdev->dev to obtain a struct vidicontext pointer. However, drmdev->dev is the exynos-drm master…
When was CVE-2026-45956 disclosed?
CVE-2026-45956 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on June 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45956 actively exploited?
CVE-2026-45956 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-45956?
CVE-2026-45956 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-45956?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45956, 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-45956

Explore →

Is Your Infrastructure Affected by CVE-2026-45956?

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