# CVE-2025-62229: Xorg: xmayland: use-after-free in xpresentnotify structure creation

> A use-after-free flaw in X.Org X server and Xwayland allows attackers to execute arbitrary code or cause a denial of service via X11 Present extension notifications.

- **Severity:** High 7.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Oct 2025
- **Updated:** 20 Apr 2026
- **Also known as:** AZL-69470, BELL-CVE-2025-62229, DEBIAN-CVE-2025-62229, GHSA-49pm-cgmh-hw25, UBUNTU-CVE-2025-62229

## What is CVE-2025-62229?

CVE-2025-62229 is a high-severity use after free vulnerability in Red Hat Enterprise Linux 10, published on 30 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### 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.

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2025-62229?


## How do I fix CVE-2025-62229?

Apply the vendor's patch.

## Is CVE-2025-62229 being exploited?

There is no known exploitation of CVE-2025-62229 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-62229 and fix it if it is affected.

What it is: CVE-2025-62229 is a high-severity use after free vulnerability in Red Hat Enterprise Linux 10, published on 30 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-62229 in the wild and no public exploit code.

Affected product: Red Hat Enterprise Linux 10. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-62229/ (Markdown: https://insights.sbomify.com/CVE-2025-62229/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-62229
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-62229
- OSV: https://osv.dev/vulnerability/CVE-2025-62229

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-62229/
Summaries are generated and may contain mistakes; the official description above is the record.