CVE-2025-26599: 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 marked just before, which leaves the validated data partly initialized and the use of an uninitialized pointer later.
Other sources
The function compCheckRedirect() may fail if it cannot allocate the backing pixmap. In that case, compRedirectWindow() will return a BadAlloc error without the validation of the window tree marked just before, which leaves the validate data partly initialized, and the use of an uninitialized pointer later.
— Red Hat
Xorg: xwayland: use of uninitialized pointer in compredirectwindow()
— Microsoft
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/xorg-serverto a version that resolves this vulnerability.Fixed in 2:1.20.11-1+deb11u15Fixed in 2:21.1.7-3+deb12u9Fixed in 2:21.1.16-1 - Upgrade
Upgrade
debian/xwaylandto a version that resolves this vulnerability.Fixed in 2:24.1.6-1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 1.20.10-15 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 24.1.6-1
Event History
Frequently Asked Questions
What is the severity of CVE-2025-26599?
CVE-2025-26599 is classified as a medium severity vulnerability due to the potential risk of uninitialized pointer access leading to application crashes.
How do I fix CVE-2025-26599?
To fix CVE-2025-26599, update to the latest version of Xwayland where the vulnerability is addressed.
What systems are affected by CVE-2025-26599?
CVE-2025-26599 affects X.Org and Xwayland installations across various Linux distributions.
What type of vulnerability is CVE-2025-26599?
CVE-2025-26599 is an access to an uninitialized pointer flaw that can lead to resource allocation failures.
Are there any known exploits for CVE-2025-26599?
As of now, there are no known active exploits for CVE-2025-26599, but it is recommended to apply patches as a precaution.