CVE-2026-23227: drm/exynos: vidi: use ctx->lock to protect struct vidi_context member variables related to memory alloc/free
In the Linux kernel, the following vulnerability has been resolved:
drm/exynos: vidi: use ctx->lock to protect struct vidi_context member variables related to memory alloc/free
Exynos Virtual Display driver performs memory alloc/free operations
without lock protection, which easily causes concurrency problem.
For example, use-after-free can occur in race scenario like this:
```
CPU0 CPU1 CPU2
---- ---- ----
vidi_connection_ioctl()
if (vidi->connection) // true
drm_edid = drm_edid_alloc(); // alloc drm_edid
...
ctx->raw_edid = drm_edid;
...
drm_mode_getconnector()
drm_helper_probe_single_connector_modes()
vidi_get_modes()
if (ctx->raw_edid) // true
drm_edid_dup(ctx->raw_edid);
if (!drm_edid) // false
...
vidi_connection_ioctl()
if (vidi->connection) // false
drm_edid_free(ctx->raw_edid); // free drm_edid
...
drm_edid_alloc(drm_edid->edid)
kmemdup(edid); // UAF!!
...
```
To prevent these vulns, at least in vidi_context, member variables related
to memory alloc/free should be protected with ctx->lock.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel bug in the Exynos virtual display driver. A local, low-privileged actor could trigger a race around display EDID memory handling, creating use-after-free risk inside the kernel. Business urgency is highest for Linux systems that include or use this Exynos DRM VIDI driver.
Executive priority
Treat as high priority for affected Linux builds, especially embedded, mobile, or appliance platforms using Exynos display components. For typical non-Exynos server fleets, validate exposure first before emergency action. No active exploitation is evidenced in the provided sources.
Technical view
The Exynos DRM VIDI driver performed memory allocation and free operations on vidi_context state without ctx->lock protection. The CVE describes a race between connection ioctl handling and connector mode probing, where raw_edid can be freed while another path duplicates it, causing use-after-free.
Likely exposure
Relevant exposure is Linux kernels with the drm/exynos VIDI virtual display driver affected by this flaw. The record lists Linux as affected and provides multiple stable kernel commit references. Practical exposure depends on kernel version, configuration, and whether the Exynos display stack is present or reachable.
Exploitation context
The CVSS vector is local, low complexity, low privileges, no user interaction, with high confidentiality, integrity, and availability impact. The source bundle marks KEV as false and provides no evidence of active exploitation or public weaponization.
Researcher notes
The vulnerability is a concurrency bug, not an input parsing issue. The core primitive is a race-induced use-after-free involving raw_edid during connection ioctl and connector probing paths. The supplied bundle does not include exploitability details beyond CVSS and the kernel fix rationale.
Mitigation direction
Apply a vendor kernel update containing the referenced stable fixes.
Confirm downstream distro kernels have backported the ctx->lock protection change.
Prioritize systems with Exynos DRM VIDI support enabled or exposed.
If no vendor update is available, follow vendor guidance for driver disablement or risk reduction.
Validation and detection
Inventory kernels and map them against vendor advisories and stable commit references.
Check whether the Exynos DRM VIDI driver is built, loaded, or reachable.
Verify patched source includes locking around vidi_context EDID alloc/free state.
Run normal kernel and display regression tests after updating.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-23227 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
9Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.