Summary
Xwayland is an X server for running X clients under Wayland.
Security Fix(es):
* xorg-x11-server: tigervnc: heap-based buffer overflow privilege escalation vulnerability (CVE-2024-9632)
* X.Org: Xwayland: Use-after-free of the root cursor (CVE-2025-26594)
* xorg: xwayland: Use-after-free in SyncInitTrigger() (CVE-2025-26601)
* xorg: xwayland: Use-after-free in PlayReleasedEvents() (CVE-2025-26600)
* xorg: xwayland: Use of uninitialized pointer in compRedirectWindow() (CVE-2025-26599)
* xorg: xwayland: Out-of-bounds write in CreatePointerBarrierClient() (CVE-2025-26598)
* xorg: xwayland: Buffer overflow in XkbChangeTypesOfKey() (CVE-2025-26597)
* xorg: xwayland: Heap overflow in XkbWriteKeySyms() (CVE-2025-26596)
* Xorg: xwayland: Buffer overflow in XkbVModMaskText() (CVE-2025-26595)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
Additional Changes:
For detailed information on changes in this release, see the AlmaLinuxRelease Notes linked from the References section.
Fixed packages 2
| Release | Package | Fixed in |
|---|---|---|
| AlmaLinux · 9 | xorg-x11-server-Xwayland | 23.2.7-3.el9_6 |
| AlmaLinux · 9 | xorg-x11-server-Xwayland-devel | 23.2.7-3.el9_6 |
Vulnerabilities 9
-
High 7.8
Xorg-x11-server: tigervnc: heap-based buffer overflow privilege escalation vulnerability
A flaw was found in the X.org server. Due to improperly tracked allocation size in _XkbSetCompatMap, a local attacker may be able to trigger a buffer overflow condition via a specially crafted payload, leading to denial of service or local privilege escalatio…
-
High 7.8
X.org: xwayland: use-after-free of the root cursor
A use-after-free flaw was found in X.Org and Xwayland. The root cursor is referenced in the X server as a global variable. If a client frees the root cursor, the internal reference points to freed memory and causes a use-after-free.
-
High 7.8
Xorg: xwayland: buffer overflow in xkbvmodmasktext()
A buffer overflow flaw was found in X.Org and Xwayland. The code in XkbVModMaskText() allocates a fixed-sized buffer on the stack and copies the names of the virtual modifiers to that buffer. The code fails to check the bounds of the buffer and would copy the…
-
High 7.8
Xorg: xwayland: heap overflow in xkbwritekeysyms()
A heap overflow flaw was found in X.Org and Xwayland. The computation of the length in XkbSizeKeySyms() differs from what is written in XkbWriteKeySyms(), which may lead to a heap-based buffer overflow.
-
High 7.8
Xorg: xwayland: buffer overflow in xkbchangetypesofkey()
A buffer overflow flaw was found in X.Org and Xwayland. If XkbChangeTypesOfKey() is called with a 0 group, it will resize the key symbols table to 0 but leave the key actions unchanged. If the same function is later called with a non-zero value of groups, thi…
-
High 7.8
Xorg: xwayland: out-of-bounds write in createpointerbarrierclient()
An out-of-bounds write flaw was found in X.Org and Xwayland. The function GetBarrierDevice() searches for the pointer device based on its device ID and returns the matching value, or supposedly NULL, if no match was found. However, the code will return the la…
-
High 7.8
Xorg: xwayland: use of uninitialized pointer in compredirectwindow()
An access to an uninitialized pointer flaw was found in X.Org and Xwayland. The function compCheckRedirect() may fail if it cannot allocate the backing pixmap. In that case, compRedirectWindow() will return a BadAlloc error without validating the window tree …
-
High 7.8
Xorg: xwayland: use-after-free in playreleasedevents()
A use-after-free flaw was found in X.Org and Xwayland. When a device is removed while still frozen, the events queued for that device remain while the device is freed. Replaying the events will cause a use-after-free.
-
High 7.8
Xorg: xwayland: use-after-free in syncinittrigger()
A use-after-free flaw was found in X.Org and Xwayland. When changing an alarm, the values of the change mask are evaluated one after the other, changing the trigger values as requested, and eventually, SyncInitTrigger() is called. If one of the changes trigge…
References
-
report
https://access.redhat.com/security/cve/CVE-2024-9632
-
report
https://access.redhat.com/security/cve/CVE-2025-26594
-
report
https://access.redhat.com/security/cve/CVE-2025-26595
-
report
https://access.redhat.com/security/cve/CVE-2025-26596
-
report
https://access.redhat.com/security/cve/CVE-2025-26597
-
report
https://access.redhat.com/security/cve/CVE-2025-26598
-
report
https://access.redhat.com/security/cve/CVE-2025-26599
-
report
https://access.redhat.com/security/cve/CVE-2025-26600
-
report
https://access.redhat.com/security/cve/CVE-2025-26601
-
report
https://bugzilla.redhat.com/2317233
-
report
https://bugzilla.redhat.com/2345248
-
report
https://bugzilla.redhat.com/2345251
-
report
https://bugzilla.redhat.com/2345252
-
report
https://bugzilla.redhat.com/2345253
-
report
https://bugzilla.redhat.com/2345254
-
report
https://bugzilla.redhat.com/2345255
-
report
https://bugzilla.redhat.com/2345256
-
report
https://bugzilla.redhat.com/2345257
-
advisory
https://errata.almalinux.org/9/ALSA-2025-7165.html