Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2026-45956

7.8 · HIGH

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_dat…

Published May 27, 2026CWE-416EPSS 0.17%

Overview

CVE-2026-45956 is a high-severity vulnerability. It was published on May 27, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical 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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refgit.kernel.org/stable/c/21ca24ba51a2c28bcc4df9d7e5a40b0eb66ab76dRefgit.kernel.org/stable/c/2987642c5213508c6c9e718324c0d5289a92c474Refgit.kernel.org/stable/c/65d1213baffa363f2eb1117b1dc7acc573b890f8Refgit.kernel.org/stable/c/875fa28690e93ed5296c31d3344556c6bb867234Refgit.kernel.org/stable/c/a540f767642f75240a6c35f6a65b69e44cfcea9dRefgit.kernel.org/stable/c/b5fc86d753dd4c281a943b92f0eef02d31af03d7Refgit.kernel.org/stable/c/d3968a0d85b211e197f2f4f06268a7031079e0d0

How CyberStrike helps

Frequently asked questions

What is CVE-2026-45956?

CVE-2026-45956 is a high-severity vulnerability. It was published on May 27, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2026-45956?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-45956?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-45956?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-45956 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2026

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999