CVE-2026-45956

Last refreshed2026-10-23

Status: UPDATED | Advisory ID: CVE-2026-45956

Key Details

CVE	CVE-2026-45956
CVSS Score / Version	7.8 (High) / CVSS v3.1
Updated	2026-10-21
CVSS Vector	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`
CVSS Prose	attack vector is local; attack complexity is low; privileges required is low; user interaction is none; scope is unchanged; confidentiality impact is high; integrity impact is high; availability impact is high.
Affected products	Linux Kernel
Classified as	CWE-416 (Use After Free)

Vendor	Product	Affected Versions	Patch Status
Linux	Linux Kernel

Vendor

Product

Affected Versions

Patch Status

Linux

Linux Kernel

Subsystems	OT Supporting Infrastructure
Sectors	All Sectors

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. (NVD)

Monitor Linux's web page for any future patch releases.

Source	Reference
NVD	https://nvd.nist.gov/vuln/detail/CVE-2026-45956
CVE	https://www.cve.org/CVERecord?id=CVE-2026-45956

Source

Reference

NVD

CVE