CVE-2026-45958 Linux CVE debrief

Who should care

Organizations running Linux systems with Exynos-based hardware utilizing the DRM VIDI driver; embedded/ARM device manufacturers; kernel maintainers and security teams tracking local privilege escalation vectors in kernel subsystems

Technical summary

The Exynos VIDI (Virtual Display) driver in the Linux kernel's DRM subsystem contained an unsafe direct dereference of a user-provided pointer in the `vidi_connection_ioctl()` function. The `vidi->edid` field, which receives a pointer from user space, was accessed directly in kernel context without validation or safe copying. This pattern permits user-space processes to supply arbitrary kernel addresses, potentially leading to arbitrary kernel memory read/write capabilities. The remediation replaces direct pointer usage with `copy_from_user()` to safely transfer EDID data into kernel-allocated memory, eliminating the unsafe dereference path.

Defensive priority

medium

Recommended defensive actions

• Apply kernel updates containing the referenced stable tree commits when available from your Linux distribution
• Verify kernel version is updated to a release incorporating the fix for CVE-2026-45958
• Review systems utilizing Exynos DRM VIDI driver functionality for exposure to this vulnerability
• Monitor NVD entry for CVSS scoring and severity assignment once analysis is completed

Evidence notes

CVE description confirms direct user pointer dereference in `vidi_connection_ioctl()` within `drm/exynos: vidi`. Multiple kernel.org stable tree commits provided as references indicate backports across supported kernel versions. No CVSS score or severity assigned by NVD at time of disclosure; status marked 'Awaiting Analysis'.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.