# CVE-2022-49737: Race condition in X server

> A race condition in the X.Org X server allows local attackers to cause a denial of service by triggering unsynchronized access to input data structures.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Mar 2025
- **Updated:** 17 Mar 2025
- **Also known as:** DEBIAN-CVE-2022-49737, GHSA-3f26-j6r7-9q8v, SUSE-SU-2025:0984-1, UBUNTU-CVE-2022-49737, openSUSE-SU-2025:14916-1

## What is CVE-2022-49737?

CVE-2022-49737 is a high-severity vulnerability in X.org X server, published on 16 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-413 (Improper Resource Locking)

## Which versions are affected by CVE-2022-49737?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `xorg-x11-server` | SUSE:Linux Enterprise Module for Basesystem 15 SP6 | All versions | 21.1.11-150600.5.9.1 |
| `xorg-x11-server` | SUSE:Linux Enterprise Module for Development Tools 15 SP6 | All versions | 21.1.11-150600.5.9.1 |
| `xorg-x11-server` | openSUSE:Leap 15.6 | All versions | 21.1.11-150600.5.9.1 |
| `xorg-x11-server` | openSUSE:Tumbleweed | All versions | 21.1.15-3.1 |

## How do I fix CVE-2022-49737?

Apply the vendor's patch.

## Is CVE-2022-49737 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-49737 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-49737 and fix it if it is affected.

What it is: CVE-2022-49737 is a high-severity vulnerability in X.org X server, published on 16 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-49737 exists.

Affected product: X.org X server. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-49737/ (Markdown: https://insights.sbomify.com/CVE-2022-49737/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-49737
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-49737
- OSV: https://osv.dev/vulnerability/CVE-2022-49737

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-49737/
Summaries are generated and may contain mistakes; the official description above is the record.