# CVE-2024-2193: Race condition in CPU

> An unauthenticated attacker can exploit a speculative race condition in modern CPUs to disclose arbitrary data from the processor.

- **Severity:** Medium 5.7 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Mar 2024
- **Updated:** 30 Apr 2025
- **Also known as:** ALPINE-CVE-2024-2193, DEBIAN-CVE-2024-2193, GHSA-3p53-237x-3cww, ROOT-OS-DEBIAN-11-CVE-2024-2193, ROOT-OS-DEBIAN-12-CVE-2024-2193, ROOT-OS-DEBIAN-13-CVE-2024-2193, ROOT-OS-UBUNTU-2204-CVE-2024-2193, UBUNTU-CVE-2024-2193

## What is CVE-2024-2193?

CVE-2024-2193 is a medium-severity vulnerability in AMD CPU, published on 15 Mar 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A Speculative Race Condition (SRC) vulnerability that impacts modern CPU architectures supporting speculative execution (related to Spectre V1) has been disclosed. An unauthenticated attacker can exploit this vulnerability to disclose arbitrary data from the CPU using race conditions to access the speculative executable code paths.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2024-2193?


## How do I fix CVE-2024-2193?

Apply the vendor's patch.

## Is CVE-2024-2193 being exploited?

There is no known exploitation of CVE-2024-2193 in the wild and no public exploit code.

Public exploit code:

- https://github.com/uthrasri/CVE-2024-2193 (github_poc): https://github.com/uthrasri/CVE-2024-2193

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-2193 and fix it if it is affected.

What it is: CVE-2024-2193 is a medium-severity vulnerability in AMD CPU, published on 15 Mar 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-2193 in the wild and no public exploit code.

Affected product: AMD CPU. 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-2024-2193/ (Markdown: https://insights.sbomify.com/CVE-2024-2193/index.md)
```

## Sources

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

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