Xwayland: Use After Free
CVE-2025-62229 is a high-severity use after free vulnerability in Xwayland from X.Org, with a CVSS 3.1 base score of 7.3 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists version 24.1.9 as the first without the flaw, so updating Xwayland to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.51% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Xwayland to 24.1.9 or a later version.
Affected products and versions
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- LowSome restricted data can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H. Scored by CNA (redhat.com).
Official description
A flaw was found in the X.Org X server and Xwayland when processing X11 Present extension notifications. Improper error handling during notification creation can leave dangling pointers that lead to a use-after-free condition. This can cause memory corruption or a crash, potentially allowing an attacker to execute arbitrary code or cause a denial of service.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Use After Free
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.
How developers prevent this class of flaw
- Choose a language that provides automatic memory management.
- When freeing pointers, be sure to set them to NULL once they are freed. However, the utilization of multiple or complex data structures may lower the usefulness of this strategy.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other references
- access.redhat.com/errata/RHSA-2025:19432
- access.redhat.com/errata/RHSA-2025:19433
- access.redhat.com/errata/RHSA-2025:19434
- access.redhat.com/errata/RHSA-2025:19435
- access.redhat.com/errata/RHSA-2025:19489
- access.redhat.com/errata/RHSA-2025:19623
- access.redhat.com/errata/RHSA-2025:19909
- access.redhat.com/errata/RHSA-2025:20958
- access.redhat.com/errata/RHSA-2025:20960
- access.redhat.com/errata/RHSA-2025:20961
- access.redhat.com/errata/RHSA-2025:21035
- access.redhat.com/errata/RHSA-2025:22040
- access.redhat.com/errata/RHSA-2025:22041
- access.redhat.com/errata/RHSA-2025:22051
- access.redhat.com/errata/RHSA-2025:22055
Other vulnerabilities in Xwayland
- 7.8 High severity
- 8.5 High severity
- 8.5 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
Recent Use After Free vulnerabilities
- 7.3 High severity
- 7.8 High severity
- 7.5 High severity
- 7.8 High severity
- 9.8 Critical severity
- 7.8 High severity
Spotted an error? Tell us.