Service interruption via unreleased XKB allocations
Published Oct 17, 2022 · Updated Apr 15, 2025
Resource leak in X.Org Server allows remote authenticated users to exhaust server memory through crafted XKB requests. ProcXkbGetKbdByName in xkb/xkb.c fails to release request-processing allocations when an error path is taken. An attacker needs an authorized X connection, and repeated requests can deplete memory until the server or host service is interrupted.
Summary
What happened
Resource leak in X.Org Server allows remote authenticated users to exhaust server memory through crafted XKB requests. ProcXkbGetKbdByName in xkb/xkb.c fails to release request-processing allocations when an error path is taken. An attacker needs an authorized X connection, and repeated requests can deplete memory until the server or host service is interrupted.
The record
- CVE
- CVE-2022-3551
- Published
- Oct 17, 2022
- Updated
- Apr 15, 2025
- Vendor
- X.Org
- Product
- X.Org Server
- Classifications
- CWE-401, T1499
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 17, 2022CVE publishedPublication date reported by the CVE source.
- Apr 15, 2025Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=n/a
What conditions does exploitation require?
What is affected?
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