CVE-2026-23227 drm/exynos: vidi: use ctx->lock to protect struct vidi_context member variables related to memory alloc/free
A race condition in the Exynos Virtual Display driver allows use-after-free, potentially enabling code execution or privilege escalation.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-23227?
CVE-2026-23227 is a high-severity use after free vulnerability in Linux kernel, published on 18 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
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.
Weakness: CWE-416
Which versions are affected by CVE-2026-23227?
It affects 1 product.
Products include Linux kernel.
How do I fix CVE-2026-23227?
Apply the vendor's patch.
Upgrade to the fixed version. These bugs are found with fuzzing and sanitisers and avoided by memory-safe languages. More about Use after free.
Is CVE-2026-23227 being exploited?
There is no known exploitation of CVE-2026-23227 in the wild and no public exploit code.
Other vulnerabilities in Linux kernel
Sources
Also known as BELL-CVE-2026-23227, DEBIAN-CVE-2026-23227, GHSA-g3vh-wfh4-fp76, ROOT-OS-DEBIAN-11-CVE-2026-23227, ROOT-OS-DEBIAN-12-CVE-2026-23227, ROOT-OS-DEBIAN-13-CVE-2026-23227 and 3 more.