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
A race condition in the Linux Exynos virtual display driver can cause kernel memory to be used after it is freed. A local, low-privileged user may be able to trigger the flaw without user interaction, potentially crashing the system or compromising confidentiality and integrity. It is not a remote network vulnerability.
Executive priority
Prioritize affected shared, kiosk, embedded, or multi-user Exynos systems where untrusted users obtain local access. Treat internet-only systems without local access as lower urgency, while still applying normal kernel maintenance. Because affected-version metadata is unclear, require technical confirmation rather than relying only on version-string scanning.
Technical view
Concurrent Exynos VIDI operations can access and free shared vidi_context memory without adequate locking. Specifically, one path may free raw_edid while the connector-mode path duplicates it, causing a kernel use-after-free. The referenced resolution protects allocation-related and free-related context members with ctx->lock. CVSS 3.1 is 7.8: local access, low complexity, low privileges, and no interaction.
Likely exposure
Exposure is most likely on Linux systems using the affected Exynos Virtual Display driver where an untrusted local user can reach the relevant DRM operations. Systems without this driver or affected code path are unlikely to be exposed. The bundled version information is broad and ambiguous, so confirm exposure using distribution advisories and kernel commit provenance.
Exploitation context
The supplied record does not establish active exploitation, and KEV is false. Exploitation requires local, low-privileged access rather than remote network access. The demonstrated condition is a race-induced kernel use-after-free; the sources do not establish reliable privilege escalation, exploit availability, or observed attacks.
Researcher notes
The race involves vidi_connection_ioctl() changing or freeing raw_edid while drm_mode_getconnector() reaches vidi_get_modes() and duplicates that object. The fix serializes relevant vidi_context memory lifecycle operations using ctx->lock. The CVSS impact claims are severe, but the bundle provides neither exploit evidence nor proof of a specific real-world outcome beyond the use-after-free condition.
Mitigation direction
Install the applicable vendor or distribution kernel update containing the referenced stable fix.
Confirm the selected update covers the system's kernel branch and Exynos VIDI implementation.
If updates are delayed, review and limit untrusted local access to relevant DRM devices.
Monitor Linux distribution guidance for corrected package versions and operational mitigations.
Validation and detection
Inventory Linux kernel versions, hardware platforms, and whether the Exynos VIDI driver is present or enabled.
Compare deployed kernel source or package provenance with the applicable referenced stable fix commit.
Verify vendor advisories identify the installed package as corrected before closing remediation.
After updating, confirm systems boot normally and required display functions remain operational.
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.