Kernel memory corruption via incorrect VIDI context lookup
Published May 27, 2026 · Updated May 27, 2026
Memory-safety errors in the Linux Kernel Exynos VIDI DRM driver allow local users to corrupt kernel memory or crash the system. vidi_connection_ioctl retrieves driver_data from the Exynos DRM master device and treats unrelated device data as a vidi_context instead of using the VIDI component pointer. Reachability requires an enabled VIDI driver, access to the primary DRM device, and passage of DRM_AUTH checks; no network path or user interaction is involved.
Summary
What happened
Memory-safety errors in the Linux Kernel Exynos VIDI DRM driver allow local users to corrupt kernel memory or crash the system. vidi_connection_ioctl retrieves driver_data from the Exynos DRM master device and treats unrelated device data as a vidi_context instead of using the VIDI component pointer. Reachability requires an enabled VIDI driver, access to the primary DRM device, and passage of DRM_AUTH checks; no network path or user interaction is involved.
The record
- CVE
- CVE-2026-45956
- Published
- May 27, 2026
- Updated
- May 27, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-416, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 27, 2026CVE publishedPublication date reported by the CVE source.
- May 27, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <5.10.253
- Affected versionversion=0 <5.15.203
- Affected versionversion=0 <6.1.167
- Affected versionversion=0 <6.18.14
- Affected versionversion=0 <6.19.4
- Affected versionversion=0 <6.6.130
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <21ca24ba51a2c28bcc4df9d7e5a40b0eb66ab76d
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2987642c5213508c6c9e718324c0d5289a92c474
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <65d1213baffa363f2eb1117b1dc7acc573b890f8
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <875fa28690e93ed5296c31d3344556c6bb867234
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a540f767642f75240a6c35f6a65b69e44cfcea9d
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b5fc86d753dd4c281a943b92f0eef02d31af03d7
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <d3968a0d85b211e197f2f4f06268a7031079e0d0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo