CVE-2026-23227: drm/exynos: vidi: use ctx->lock to protect struct vidi_context member variables related to memory alloc/free

Published Feb 18, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

drm/exynos: vidi: use ctx->lock to protect struct vidicontext 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 ---- ---- ---- vidiconnectionioctl() if (vidi->connection) // true drmedid = drmedidalloc(); // alloc drmedid ... ctx->rawedid = drmedid; ... drmmodegetconnector() drmhelperprobesingleconnectormodes() vidigetmodes() if (ctx->rawedid) // true drmediddup(ctx->rawedid); if (!drmedid) // false ... vidiconnectionioctl() if (vidi->connection) // false drmedidfree(ctx->rawedid); // free drmedid ... drmedidalloc(drmedid->edid) kmemdup(edid); // UAF!! ...

To prevent these vulns, at least in vidicontext, member variables related to memory alloc/free should be protected with ctx->lock.

Affected Software

5 affected componentsFixes available
Linux Linux kernel
Linux Linux kernel>=3.6<6.12.77
Linux Linux kernel>=6.13<6.18.11
Linux Linux kernel>=6.19<6.19.1
debian/linux
6.1.176-16.1.190-16.12.107-16.12.115-27.2.12-17.2.15-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.113-1Fixed in 7.2.12-1Fixed in 7.2.13-1
  2. Compensating control

    In the Exynos Virtual Display driver, protect vidi_context member variables related to memory allocation and freeing with ctx->lock, including accesses to ctx->raw_edid and the associated drm_edid allocation, duplication, and free operations.

Event History

Feb 18, 2026
CVE Published
via MITRE·02:53 PM
Data Sourced
via MITRE·02:53 PM
DescriptionSeverity
Data Sourced
via NVD·04:22 PM
RemedyDescriptionSeverityWeaknessAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

What is the severity of CVE-2026-23227?

The severity of CVE-2026-23227 is classified as medium due to potential exploitation risks.

2

How do I fix CVE-2026-23227?

To fix CVE-2026-23227, update to the latest version of the Linux kernel that includes the patch for this vulnerability.

3

What systems are affected by CVE-2026-23227?

CVE-2026-23227 affects the Linux Kernel, specifically those using Exynos video driver components.

4

What does CVE-2026-23227 exploit?

CVE-2026-23227 exploits a flaw related to memory allocation and free processes within the Exynos video driver.

5

Is CVE-2026-23227 a remote exploit risk?

CVE-2026-23227 does not present a typical remote exploit risk, as it requires local access to the affected system.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203