drm/exynos: vidi: use priv->vidi_dev for ctx lookup in vidi_connection_ioctl()
CVE-2026-45956 · published 27 May 2026
How serious is it
- Severity: high, CVSS score 7.8 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-45956?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: cf67cc9a29ac19c98bc4fa0e6d14b0c1f592d322 to < 2987642c5213508c6c9e718324c0d5289a92c474, cf67cc9a29ac19c98bc4fa0e6d14b0c1f592d322 to < 65d1213baffa363f2eb1117b1dc7acc573b890f8, cf67cc9a29ac19c98bc4fa0e6d14b0c1f592d322 to < 875fa28690e93ed5296c31d3344556c6bb867234, cf67cc9a29ac19c98bc4fa0e6d14b0c1f592d322 to < 21ca24ba51a2c28bcc4df9d7e5a40b0eb66ab76d
- Linux Linux: 4.3
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
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.
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/2987642c5213508c6c9e718324c0d5289a92c474
- git.kernel.org/stable/c/65d1213baffa363f2eb1117b1dc7acc573b890f8
- git.kernel.org/stable/c/875fa28690e93ed5296c31d3344556c6bb867234
- git.kernel.org/stable/c/21ca24ba51a2c28bcc4df9d7e5a40b0eb66ab76d
- git.kernel.org/stable/c/e1aed617eb80b49eac2f8c7bb7a0990f641dd59b
- git.kernel.org/stable/c/b5fc86d753dd4c281a943b92f0eef02d31af03d7
- git.kernel.org/stable/c/a540f767642f75240a6c35f6a65b69e44cfcea9d
- git.kernel.org/stable/c/d3968a0d85b211e197f2f4f06268a7031079e0d0
Merged from CVE List. Last updated 25 Oct 2026. All vulnerabilities · RSS · JSON