CVE-2026-50257
What it is
A use-after-free flaw was found in the X.Org X server and Xwayland in miSyncDestroyFence(). A client that sets up multiple fence triggers can trigger a use-after-free function pointer call. An attacker would connect to the X server to set up a fence and await that fence, then a second X connection destroys the fence, causing the use-after-free. This may be used to crash the server, or for privilege escalation if the X server runs as root.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 0.1% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.1% in the next 30 days (EPSS).
- Severity: 7.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.1% · EPSS, next 30 days
- Weakness
- CWE-416 · Use after free
- Record status
- Modified
Affected
- x.org X Server < 21.1.23
- x.org Xwayland < 24.1.12
- Redhat Enterprise Linux 7.0
- Redhat Enterprise Linux 8.0
- Redhat Enterprise Linux 9.0
- Redhat Enterprise Linux 10.0
Attack profile CVSS 3.1 · 7.8
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-50257.md and follow it. Check whether this project is affected by CVE-2026-50257. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
References
- https://access.redhat.com/errata/RHSA-2026:26562
- https://access.redhat.com/errata/RHSA-2026:26566
- https://access.redhat.com/errata/RHSA-2026:26590
- https://access.redhat.com/errata/RHSA-2026:26610
- https://access.redhat.com/errata/RHSA-2026:26709
- https://access.redhat.com/errata/RHSA-2026:28923
- https://access.redhat.com/errata/RHSA-2026:29844
- https://access.redhat.com/errata/RHSA-2026:36083
- https://access.redhat.com/errata/RHSA-2026:36085
- https://access.redhat.com/errata/RHSA-2026:36086
- https://access.redhat.com/errata/RHSA-2026:36087
- https://access.redhat.com/errata/RHSA-2026:36632
- https://access.redhat.com/errata/RHSA-2026:36633
- https://access.redhat.com/errata/RHSA-2026:36634
- https://access.redhat.com/errata/RHSA-2026:36768
- https://access.redhat.com/errata/RHSA-2026:36791
- https://access.redhat.com/errata/RHSA-2026:36792
- https://access.redhat.com/errata/RHSA-2026:36798
- https://access.redhat.com/errata/RHSA-2026:38502
- https://access.redhat.com/errata/RHSA-2026:38810
- https://access.redhat.com/errata/RHSA-2026:46377
- https://access.redhat.com/errata/RHSA-2026:46382
- https://access.redhat.com/errata/RHSA-2026:46385
- https://access.redhat.com/errata/RHSA-2026:46392
- https://access.redhat.com/errata/RHSA-2026:46456