CVE-2026-45956 json
drm/exynos: vidi: use priv->vidi_dev for ctx lookup in vidi_connection_ioctl()
published 2026-05-27 5 mo ago modified 2026-10-21 19 d ago also EUVD-2026-32240
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 2%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 5.10.253, 5.15.203, 6.1.167, 6.6.130, 6.12.114, 6.18.14, 6.19.4, 7.0
- linux Debian 12 6.1.170-1
- linux Debian 13 6.12.115-2
- linux Debian 14 6.18.14-1
debian advisories DEBIAN-CVE-2026-45956
- linux Ubuntu 22.04 LTS 5.15.0-186.196
- linux Ubuntu 24.04 LTS 6.8.0-136.136
- linux-aws Ubuntu 22.04 LTS 5.15.0-1112.119
- linux-aws Ubuntu 24.04 LTS 6.8.0-1061.64
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1112.122
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1064.72
- linux-gke Ubuntu 22.04 LTS 5.15.0-1108.114
- linux-gke Ubuntu 24.04 LTS 6.8.0-1059.67
ubuntu advisories UBUNTU-CVE-2026-45956
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/2987642c5213508c6c9e718324c0d5289a92c474 commit
- git.kernel.org/stable/c/65d1213baffa363f2eb1117b1dc7acc573b890f8 commit
- git.kernel.org/stable/c/875fa28690e93ed5296c31d3344556c6bb867234 commit
- git.kernel.org/stable/c/21ca24ba51a2c28bcc4df9d7e5a40b0eb66ab76d commit
- git.kernel.org/stable/c/e1aed617eb80b49eac2f8c7bb7a0990f641dd59b commit
- git.kernel.org/stable/c/b5fc86d753dd4c281a943b92f0eef02d31af03d7 commit
- git.kernel.org/stable/c/a540f767642f75240a6c35f6a65b69e44cfcea9d commit
- git.kernel.org/stable/c/d3968a0d85b211e197f2f4f06268a7031079e0d0 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-45956 updated
kernel: drm/exynos: vidi: use priv->vidi_dev for ctx lookup in vidi_connection_ioctl()
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.13% chance of exploitation in the next 30 days, higher than 2% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-416 Use After Free
- Technology feeds
References
-
git.kernel.org
/stable/c/2987642c5213508c6c9e718324c0d5289a92c474
patch
-
git.kernel.org
/stable/c/65d1213baffa363f2eb1117b1dc7acc573b890f8
patch
-
git.kernel.org
/stable/c/875fa28690e93ed5296c31d3344556c6bb867234
patch
-
git.kernel.org
/stable/c/21ca24ba51a2c28bcc4df9d7e5a40b0eb66ab76d
patch
- git.kernel.org /stable/c/e1aed617eb80b49eac2f8c7bb7a0990f641dd59b
-
git.kernel.org
/stable/c/b5fc86d753dd4c281a943b92f0eef02d31af03d7
patch
-
git.kernel.org
/stable/c/a540f767642f75240a6c35f6a65b69e44cfcea9d
patch
-
git.kernel.org
/stable/c/d3968a0d85b211e197f2f4f06268a7031079e0d0
patch
Sources
- CVE List CVE-2026-45956
- NVD CVE-2026-45956
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.