CVE-2026-56000: xorg-x11-server / xwayland GLX contextTags Use-After-Free in CommonMakeCurrent()

Published Jul 1, 2026
·
Updated

CommonMakeCurrent() in the GLX dispatch layer captures a pointer into the per-client cl->contextTags array by calling GlxLookupContextTag(). This returns a direct pointer into an array later realloced. If realloc() moves the buffer to a new location, the previously captured oldTag pointer becomes dangling. The subsequent GlxFreeContextTag(oldTag) then writes zeros into freed heap memory (use-after-free). Five fields are zeroed at fixed offsets (16, 24, 32, 36, 40 bytes) within the stale slot. A malicious client can force the realloc by creating 16 GLX contexts with MakeCurrent(oldContextTag=0) to fill all tag slots to capacity, then issuing a 17th MakeCurrent with a non-zero oldContextTag. This triggers the realloc while oldTag points into the old buffer. The attack requires only 34 X11 requests (17 CreateContext + 17 MakeCurrent) from a single client.

Other sources

Local attackers with a X connection able to provide GLX commit to the X server xorg-server before 21.2.24 and xwayland before 24.1.13 could cause a Heap Use After Free, due to CommonMakeCurrent() pointing into potentially reallocated memory.

MITRE

xorg-x11-server / xwayland GLX contextTags Use-After-Free in CommonMakeCurrent()

Microsoft

Affected Software

5 affected componentsFixes available
X.Org xorg-server<21.2.24
xorg-x11-server/xwayland<24.1.13
X.Org X Server<21.2.24
X.Org Xwayland<24.1.13
Microsoft azl3 xorg-x11-server-Xwayland 24.1.12-1<24.1.13-1
24.1.13-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 24.1.13-1
  2. Upgrade

    Upgrade xorg-x11-server (GLX contextTags) to a version that resolves this vulnerability.

    Fixed in 21.2.24
  3. Upgrade

    Upgrade xwayland (GLX contextTags) to a version that resolves this vulnerability.

    Fixed in 24.1.13

Event History

Jul 1, 2026
Data Sourced
via Red Hat·08:41 PM
DescriptionSeverityAffected Software
Jul 8, 2026
CVE Published
via MITRE·07:36 AM
Data Sourced
via MITRE·07:36 AM
DescriptionWeakness
Data Sourced
via NVD·09:16 AM
RemedyDescriptionSeverityWeaknessAffected Software
Jul 9, 2026
Data Sourced
via Microsoft·08:02 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·08:02 AM
DescriptionSeverity
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-56000?

CVE-2026-56000 has a critical severity rating of 9.

2

How do I fix CVE-2026-56000?

To fix CVE-2026-56000, update xorg-server to version 21.2.24 or higher and xwayland to version 24.1.13 or higher.

3

What types of systems are affected by CVE-2026-56000?

CVE-2026-56000 affects systems running xorg-server prior to version 21.2.24 and xwayland prior to version 24.1.13.

4

What kind of vulnerability is CVE-2026-56000?

CVE-2026-56000 is classified as a Use After Free vulnerability.

5

What is the potential impact of exploiting CVE-2026-56000?

Exploiting CVE-2026-56000 could allow local attackers to cause a Heap Use After Free, leading to possibly executing arbitrary code.

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