Use After FreeWeakness · CWE-416

CVE-2025-62229

HIGH · 7.3 CVSS v3.1 Published 2025-10-30

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

75/100

Remediation priority · High

Zero-click

Official description

NVD · unedited

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.

Technical summary

dbcve analysis · high confidence

The X.Org X server and Xwayland contain a use-after-free vulnerability in the X11 Present extension notification handling. Improper error handling during notification creation fails to properly clean up pointers, leaving dangling pointers that can be dereferenced after memory has been freed, leading to memory corruption and potential code execution.

MitigationApply the vendor patch for CVE-2025-62229 to the X.Org X server and Xwayland. If no patch is available, consider disabling the Present extension or upgrading to a patched version.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown

From the vector

Attack vector: Local
Complexity: Low
Privileges: Low
User interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: High
Availability: High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify if X.Org X server or Xwayland is running

Run 'ps aux | grep -E "Xorg|Xwayland"' or check system logs for X server processes

Affected if The system is running either X.Org X server or Xwayland as the display server
Determine the installed X.Org X server version

Run 'Xorg -version' or check the package manager (e.g., 'dpkg -l xserver-xorg-core' on Debian/Ubuntu, 'rpm -qa xorg-x11-server' on RHEL/CentOS)

Affected if The installed version matches the affected version range for CVE-2025-62229 when compared to the vulnerability advisory
Determine the installed Xwayland version

Run 'Xwayland --version' or check the package manager (e.g., 'dpkg -l xwayland' or 'rpm -qa xwayland')

Affected if The installed version matches the affected version range for CVE-2025-62229 when compared to the vulnerability advisory
Verify if the Present extension is loaded

Run 'xdpyinfo -queryExtensions' to list loaded extensions and look for 'Present' in the output, or check X server configuration files for explicit extension loading

Affected if The Present extension is listed as loaded or enabled in the X server configuration
Check for crash logs or memory corruption indicators

Review system logs (/var/log/syslog, /var/log/Xorg.0.log) and application crash logs for segfaults, memory corruption errors, or unexpected X server restarts occurring around the time of the vulnerability disclosure

Affected if The system shows crash patterns consistent with use-after-free in the Present extension notification handling

A user is affected if they are running a version of X.Org X server or Xwayland within the affected range AND the Present extension is enabled, as the vulnerability requires both conditions to be exploitable.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Apply the vendor patch for CVE-2025-62229 to the X.Org X server and Xwayland. If no patch is available, consider disabling the Present extension or upgrading to a patched version.

Have this fixed Scoped from the published advisory

Consultation3.0 h
Implementation6.0 h
Testing4.0 h
Review / QA3.0 h

16.0 hours of engineering $2,820

Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2025-62229 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-62229 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2025-62229?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here

Verified mitigations, workarounds, and config changes
Version or environment caveats, and links to real fixes
No weaponised exploit code, or anything meant to cause harm
No spam, self-promotion, credentials, or personal data

At a glance

A fix existsA vendor remedy is published

Severity 7.3 High

Exploit likelihood EPSS, next 30 days 0.5%

Remediation

A high-priority fix

Have this fixed 16 hrs · Moderate

Typical engagement from $2,820

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2025-62229 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

Check your environment

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References