CVE-2022-49737

In X.Org X server 20.11 through 21.1.16, when a client application uses easystroke for mouse gestures, the main thread modifies various data structures used by the input thread without acquiring a lock, aka a race condition. In particular, AttachDevice in dix/devices.c does not acquire an input lock.

Published: 2025-03-16 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-49737 is rated Low Risk (39.9/100): CVSS High severity, with low exploitation likelihood (EPSS 0.10%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2022-49737

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-04-24 0.16% 0.10% -0.06%
2 2025-12-10 0.12% 0.16% +0.03%
3 2025-11-21 — 0.12% —

Full EPSS history (10 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-49737

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.7 3.1 HIGH
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 5.3 [email protected]

Weakness enumeration for CVE-2022-49737

OS Trackers for CVE-2022-49737

vendor priority summary link
debian not yet assigned CVE-2022-49737 not yet assigned priority: Debian including 1 source packages (xorg-server), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 3, open 2. https://security-tracker.debian.org/tracker/CVE-2022-49737
suse medium CVE-2022-49737 severity moderate: SUSE including 254 source package names (21:xorg-x11-server-21.1.11-150600.5.9.1, 21:xorg-x11-server-Xvfb-21.1.11-150600.5.9.1, …), 317 product×package rows across 37 product lines (Container suse/kiosk/xorg, Image SLES15-SP6-SAP, … (37 product lines)): Known Affected 231, Known Not Affected 49, Fixed 37. https://www.suse.com/security/cve/CVE-2022-49737/
ubuntu low CVE-2022-49737 low priority: Ubuntu including 7 source packages (xorg, xorg-hwe-16.04, …), 58 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 25, needs-triage 15, not-affected 13, ignored 4, released 1. https://ubuntu.com/security/CVE-2022-49737

Affected software / configurations for CVE-2022-49737

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2022-49737

cvelogic Threat Intelligence