CVE-2026-23227
Use-After-Free in Linux Exynos Vidi Driver Due to Missing Lock
Publication date: 2026-02-18
Last updated on: 2026-04-18
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 6.19 (inc) to 6.19.1 (exc) |
| linux | linux_kernel | From 6.13 (inc) to 6.18.11 (exc) |
| linux | linux_kernel | From 3.6 (inc) to 6.12.77 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-416 | The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the Linux kernel's Exynos Virtual Display driver (drm/exynos: vidi). The driver performs memory allocation and free operations without proper lock protection, which leads to concurrency problems.
Specifically, member variables related to memory allocation and freeing in the vidi_context structure are accessed without using the ctx->lock, causing race conditions.
An example race scenario involves multiple CPUs where one CPU allocates memory and assigns it to ctx->raw_edid, while another CPU may free that memory concurrently, leading to a use-after-free (UAF) condition.
To fix this, the vulnerability was resolved by ensuring that memory-related member variables in vidi_context are protected by ctx->lock to prevent concurrent access issues.
How can this vulnerability impact me? :
This vulnerability can cause concurrency problems such as use-after-free conditions in the Exynos Virtual Display driver.
Use-after-free bugs can lead to system instability, crashes, or potentially allow attackers to execute arbitrary code or cause denial of service by exploiting the race condition.
Therefore, if you are using affected Linux kernels with the Exynos Virtual Display driver, your system could be vulnerable to these issues until patched.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, ensure that the Exynos Virtual Display driver (vidi) in the Linux kernel uses proper locking mechanisms to protect memory allocation and free operations.
Specifically, member variables related to memory allocation and freeing in vidi_context should be protected with ctx->lock to prevent concurrency issues such as use-after-free.