Use After Free Affecting linux-aws-6.12 package, versions <6.12.78-r0


Severity

Recommended
0.0
high
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.01% (1st percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Use After Free vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-CHAINGUARDLATEST-LINUXAWS612-15850113
  • published30 Mar 2026
  • disclosed18 Feb 2026

Introduced: 18 Feb 2026

CVE-2026-23227  (opens in a new tab)
CWE-416  (opens in a new tab)

How to fix?

Upgrade Chainguard linux-aws-6.12 to version 6.12.78-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream linux-aws-6.12 package and not the linux-aws-6.12 package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

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-&gt;connection) // true
      drm_edid = drm_edid_alloc(); // alloc drm_edid
      ...
      ctx-&gt;raw_edid = drm_edid;
      ...
                                drm_mode_getconnector()
                                  drm_helper_probe_single_connector_modes()
                                    vidi_get_modes()
                                      if (ctx-&gt;raw_edid) // true
                                        drm_edid_dup(ctx-&gt;raw_edid);
                                          if (!drm_edid) // false
                                          ...
                vidi_connection_ioctl()
                  if (vidi-&gt;connection) // false
                    drm_edid_free(ctx-&gt;raw_edid); // free drm_edid
                    ...
                                          drm_edid_alloc(drm_edid-&gt;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.

CVSS Base Scores

version 3.1