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

Published May 27, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

drm/exynos: vidi: use priv->vididev for ctx lookup in vidiconnectionioctl()

vidiconnectionioctl() retrieves the driverdata from drmdev->dev to obtain a struct vidicontext pointer. However, drmdev->dev is the exynos-drm master device, and the driverdata 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 exynosdrmprivate->vididev during bind/unbind, and then read this exynosdrmprivate->vididev within ioctl() to obtain the correct struct vidicontext pointer.

Affected Software

8 affected components
The Linux Foundation Linux kernel (drm/exynos vidi)
Microsoft azl3 kernel 6.6.139.1-1
Linux Linux kernel>=4.3<5.10.253
Linux Linux kernel>=5.11<5.15.203
Linux Linux kernel>=5.16<6.1.167
Linux Linux kernel>=6.2<6.6.130
Linux Linux kernel>=6.7<6.18.14
Linux Linux kernel>=6.19<6.19.4

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    Update the drm/exynos vidi code so that vidi_connection_ioctl() uses priv->vidi_dev for ctx lookup, and during bind/unbind store/delete the vidi device pointer in exynos_drm_private->vidi_dev (rather than relying on drm_dev->dev->driver_data from the master device).

    Linux kernel (drm/exynos vidi) drm/exynos: vidi: use priv->vidi_dev for ctx lookup in vidi_connection_ioctl() = Implement priv->vidi_dev usage for ctx lookup in vidi_connection_ioctl() instead of using drm_dev->dev->driver_data

Event History

May 27, 2026
CVE Published
via MITRE·12:18 PM
Data Sourced
via MITRE·12:18 PM
DescriptionSeverity
Data Sourced
via NVD·02:17 PM
RemedyDescriptionSeverityWeaknessAffected Software
May 28, 2026
Data Sourced
via Microsoft·08:10 AM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-45956?

The severity of CVE-2026-45956 is high with a score of 7.1.

2

How do I fix CVE-2026-45956?

To fix CVE-2026-45956, upgrade to the latest version of the Linux kernel that addresses this vulnerability.

3

What type of vulnerabilities are associated with CVE-2026-45956?

CVE-2026-45956 is associated with use after free and null pointer dereference vulnerabilities.

4

What are the potential impacts of CVE-2026-45956?

The potential impacts of CVE-2026-45956 include system crashes and potential unauthorized access to sensitive data.

5

In which software does CVE-2026-45956 appear?

CVE-2026-45956 appears in the Linux Foundation Linux kernel and Microsoft azl3 kernel.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203