X server crash via freed XSYNC triggers
Published Apr 23, 2026 · Updated Apr 23, 2026
Use-after-free in the XSYNC fence logic in Red Hat Enterprise Linux allows local users with X11 server access to crash the server. The miSyncTriggerFence() loop calls TriggerFence(), which can invoke SyncAwaitTriggerFired() to free the entire await resource while later trigger-list entries remain queued for processing. Access to the X11 server is required; exploitation needs no user interaction and causes a crash, with memory corruption possible in some configurations.
Summary
What happened
Use-after-free in the XSYNC fence logic in Red Hat Enterprise Linux allows local users with X11 server access to crash the server. The miSyncTriggerFence() loop calls TriggerFence(), which can invoke SyncAwaitTriggerFired() to free the entire await resource while later trigger-list entries remain queued for processing. Access to the X11 server is required; exploitation needs no user interaction and causes a crash, with memory corruption possible in some configurations.
The record
- CVE
- CVE-2026-34001
- Published
- Apr 23, 2026
- Updated
- Apr 23, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat Enterprise Linux 6
- Classifications
- CWE-825, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 23, 2026CVE publishedPublication date reported by the CVE source.
- Apr 23, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo