CVE-2026-45956 - Vulnerability Details

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

Description

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.

Published: 2026-05-27

Score: n/a

EPSS: < 1% Very Low

KEV: No

Impact:

Action:

Analysis

Impact

The Exynos DRM driver in the Linux kernel contains an error in vidi_connection_ioctl where the driver data is incorrectly taken from the master DRM device instead of the specific vidi component. This mis‑lookup can trigger null pointer dereferences, out‑of‑bounds memory accesses, and use‑after‑free conditions, all of which can corrupt kernel memory and potentially lead to a system crash. Based on the description, it is inferred that kernel memory corruption could lead to elevated privileges, but this claim is not explicitly stated in the CVE data.

Affected Systems

Any Linux kernel that includes the Exynos DRM subsystem and has not applied the upstream fix that replaces the lookup with priv->vidi_dev is affected. This includes all kernels running on Exynos SoCs before the patch, such as many Android devices and embedded boards that use the Exynos DRM driver.

Risk and Exploitability

The EPSS score is not available and the vulnerability is not listed in the CISA KEV catalog. No CVSS score is publicly published. The description mentions the possibility of null pointer dereferences, out‑of‑bounds errors, and use‑after‑free conditions. Based on the description, it is inferred that exploitation requires local access to the vidi ioctl interface, but the exact attack vector is not detailed.

Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).

Vendor Product Default status Versions

Linux

unaffected

Version	Status	Constraints
`1da177e4c3f41524e886b7f1b8a0c1fc7321cac2`	affected	< 2987642c5213508c6c9e718324c0d5289a92c474
`1da177e4c3f41524e886b7f1b8a0c1fc7321cac2`	affected	< 65d1213baffa363f2eb1117b1dc7acc573b890f8
`1da177e4c3f41524e886b7f1b8a0c1fc7321cac2`	affected	< 875fa28690e93ed5296c31d3344556c6bb867234
`1da177e4c3f41524e886b7f1b8a0c1fc7321cac2`	affected	< 21ca24ba51a2c28bcc4df9d7e5a40b0eb66ab76d
`1da177e4c3f41524e886b7f1b8a0c1fc7321cac2`	affected	< b5fc86d753dd4c281a943b92f0eef02d31af03d7
`1da177e4c3f41524e886b7f1b8a0c1fc7321cac2`	affected	< a540f767642f75240a6c35f6a65b69e44cfcea9d
`1da177e4c3f41524e886b7f1b8a0c1fc7321cac2`	affected	< d3968a0d85b211e197f2f4f06268a7031079e0d0
`0`	affected	< 5.10.253
`0`	affected	< 5.15.203
`0`	affected	< 6.1.167
`0`	affected	< 6.6.130
`0`	affected	< 6.18.14
`0`	affected	< 6.19.4

Linux

affected

Version	Status	Constraints
`5.10.253`	unaffected	≤ 5.10.*
`5.15.203`	unaffected	≤ 5.15.*
`6.1.167`	unaffected	≤ 6.1.*
`6.6.130`	unaffected	≤ 6.6.*
`6.18.14`	unaffected	≤ 6.18.*
`6.19.4`	unaffected	≤ 6.19.*
`7.0`	unaffected	≤ *

No data.

Vendor Product Confidence Versions

Linux

Linux Kernel

99%

Version	Status	Scheme	Platform
`[1da177e4c3f41524e886b7f1b8a0c1fc7321cac2,2987642c5213508c6c9e718324c0d5289a92c474)`	affected	code_commit	—
`[1da177e4c3f41524e886b7f1b8a0c1fc7321cac2,65d1213baffa363f2eb1117b1dc7acc573b890f8)`	affected	code_commit	—
`[1da177e4c3f41524e886b7f1b8a0c1fc7321cac2,875fa28690e93ed5296c31d3344556c6bb867234)`	affected	code_commit	—
`[1da177e4c3f41524e886b7f1b8a0c1fc7321cac2,21ca24ba51a2c28bcc4df9d7e5a40b0eb66ab76d)`	affected	code_commit	—
`[1da177e4c3f41524e886b7f1b8a0c1fc7321cac2,b5fc86d753dd4c281a943b92f0eef02d31af03d7)`	affected	code_commit	—
`[1da177e4c3f41524e886b7f1b8a0c1fc7321cac2,a540f767642f75240a6c35f6a65b69e44cfcea9d)`	affected	code_commit	—
`[1da177e4c3f41524e886b7f1b8a0c1fc7321cac2,d3968a0d85b211e197f2f4f06268a7031079e0d0)`	affected	code_commit	—
`[0,5.10.253)`	affected	semver	—
`[0,5.15.203)`	affected	semver	—
`[0,6.1.167)`	affected	semver	—
`[0,6.6.130)`	affected	semver	—
`[0,6.18.14)`	affected	semver	—
`[0,6.19.4)`	affected	semver	—

Linux

Linux Kernel

99%

Version	Status	Scheme	Platform
`[5.10.253,5.10.*]`	unaffected	semver	—
`[5.15.203,5.15.*]`	unaffected	semver	—
`[6.1.167,6.1.*]`	unaffected	semver	—
`[6.6.130,6.6.*]`	unaffected	semver	—
`[6.18.14,6.18.*]`	unaffected	semver	—
`[6.19.4,6.19.*]`	unaffected	semver	—
`[7.0,*]`	unaffected	generic	—

Found an issue or want to improve our Enrichment? You can suggest it directly by opening an issue on our dedicated GitHub repository .

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

Update the kernel to a release that includes the upstream fix for vidi_connection_ioctl, such as the commit that uses priv->vidi_dev for context lookup.
If a kernel upgrade is not immediately possible, disable or unload the exynos_drm module to remove the vulnerable ioctl interface from the system.
Restrict access to the Exynos DRM device node (e.g., by setting ownership to root and using SELinux or AppArmor to limit it to trusted processes.

Generated by OpenCVE AI on May 28, 2026 at 05:48 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

No CVSS v4.0

No CVSS v3.1

No CVSS v3.0

No CVSS v2

This CVE is not in the KEV list.

The EPSS score is 0.00024.

Key SSVC decision points have not yet been added.

References

Link	Providers
https://git.kernel.org/stable/c/21ca24ba51a2c28bcc4df9d7e5a40b0eb66ab76d
https://git.kernel.org/stable/c/2987642c5213508c6c9e718324c0d5289a92c474
https://git.kernel.org/stable/c/65d1213baffa363f2eb1117b1dc7acc573b890f8
https://git.kernel.org/stable/c/875fa28690e93ed5296c31d3344556c6bb867234
https://git.kernel.org/stable/c/a540f767642f75240a6c35f6a65b69e44cfcea9d
https://git.kernel.org/stable/c/b5fc86d753dd4c281a943b92f0eef02d31af03d7
https://git.kernel.org/stable/c/d3968a0d85b211e197f2f4f06268a7031079e0d0
https://lore.kernel.org/linux-cve-announce/2026052732-CVE-2026-45956-50e2@gregkh/T
https://nvd.nist.gov/vuln/detail/CVE-2026-45956
https://www.cve.org/CVERecord?id=CVE-2026-45956

History

Thu, 28 May 2026 04:00:00 +0000

Type	Values Removed	Values Added
Weaknesses	CWE-119 CWE-416 CWE-690

Thu, 28 May 2026 00:15:00 +0000

Type	Values Removed	Values Added
Weaknesses		CWE-466
References		https://lore.kernel.org/linux-cve-announce/2026052732-CVE-2026-45956-50e2@gregkh/T https://nvd.nist.gov/vuln/detail/CVE-2026-45956 https://www.cve.org/CVERecord?id=CVE-2026-45956

Wed, 27 May 2026 21:00:00 +0000

Type	Values Removed	Values Added
Weaknesses		CWE-119 CWE-416 CWE-690

Wed, 27 May 2026 14:15:00 +0000

Type	Values Removed	Values Added
Description		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.
Title		drm/exynos: vidi: use priv->vidi_dev for ctx lookup in vidi_connection_ioctl()
First Time appeared		Linux Linux linux Kernel
CPEs		cpe:2.3:o:linux:linux_kernel::::::::
Vendors & Products		Linux Linux linux Kernel
References		https://git.kernel.org/stable/c/21ca24ba51a2c28bcc4df9d7e5a40b0eb66ab76d https://git.kernel.org/stable/c/2987642c5213508c6c9e718324c0d5289a92c474 https://git.kernel.org/stable/c/65d1213baffa363f2eb1117b1dc7acc573b890f8 https://git.kernel.org/stable/c/875fa28690e93ed5296c31d3344556c6bb867234 https://git.kernel.org/stable/c/a540f767642f75240a6c35f6a65b69e44cfcea9d https://git.kernel.org/stable/c/b5fc86d753dd4c281a943b92f0eef02d31af03d7 https://git.kernel.org/stable/c/d3968a0d85b211e197f2f4f06268a7031079e0d0

Subscriptions

Linux Linux Kernel

MITRE

Status: PUBLISHED

Assigner: Linux

Published: 2026-05-27T12:18:11.972Z

Updated: 2026-05-27T12:18:11.972Z

Reserved: 2026-05-13T15:03:33.088Z

Link: CVE-2026-45956

Vulnrichment

No data.

NVD

Status : Awaiting Analysis

Published: 2026-05-27T14:17:12.157

Modified: 2026-05-27T14:48:03.013

Link: CVE-2026-45956

Redhat

Severity :

Publid Date: 2026-05-27T00:00:00Z

Links: CVE-2026-45956 - Bugzilla

OpenCVE Enrichment

Updated: 2026-05-28T06:00:11Z

Weaknesses

CWE-466

Impact

Affected Systems

Risk and Exploitability

Tracking

Subscriptions

JSON object

JSON object

JSON object

JSON object

JSON object