cve.bz

CVE-2024-2193 (GhostRace) Race Condition

5.7 mediumEPSS 1.3%

Known as GhostRace

Medium (5.7). EPSS 1.3% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

5.7 medium
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N
EPSS
1.3% (unchanged from 1.3% a week ago; 1.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 71st percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2024-07-18. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization (Race Condition)
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2024-2193 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-2193?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-2193?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2024-2193 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
AMD CPUSee advisory AMD-SB-7016
Xenconsult Xen advisory XSA-453

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12xen4.17.5+23-ga4e5191dc0-1DEBIAN-CVE-2024-2193 DSA-5836-1
Debian12, 13, 14linuxno fix listedDEBIAN-CVE-2024-2193
Debian13, 14xen4.19.1-1DEBIAN-CVE-2024-2193
Ubuntu16.04:LTSxen, linux-hwe-edgeno fix listedUBUNTU-CVE-2024-2193
Ubuntu18.04:LTSxen, linux-gcp, linux-hwe and 13 moreno fix listedUBUNTU-CVE-2024-2193
Ubuntu20.04:LTSxen, linux-gke, linux-gkeop and 27 moreno fix listedUBUNTU-CVE-2024-2193
Ubuntu22.04:LTSxen, linux, linux-aws and 58 moreno fix listedUBUNTU-CVE-2024-2193
Ubuntu24.04:LTSxen, linux, linux-aws and 42 moreno fix listedUBUNTU-CVE-2024-2193
Ubuntu25.10xen, linux, linux-aws and 7 moreno fix listedUBUNTU-CVE-2024-2193
UbuntuNvidia-BlueField:22.04:LTSlinux-bluefieldno fix listedUBUNTU-CVE-2024-2193
UbuntuPro:14.04:LTSlinux, linux-aws, linux-azure and 1 moreno fix listedUBUNTU-CVE-2024-2193
UbuntuPro:16.04:LTSlinux, linux-aws, linux-gcp and 5 moreno fix listedUBUNTU-CVE-2024-2193
UbuntuPro:18.04:LTSlinux, linux-aws, linux-kvm and 10 moreno fix listedUBUNTU-CVE-2024-2193
UbuntuPro:20.04:LTSlinux, linux-aws, linux-gcp and 19 moreno fix listedUBUNTU-CVE-2024-2193
UbuntuPro:FIPS-preview:22.04:LTS, Pro:FIPS-updates:18.04:LTS, Pro:FIPS-updates:20.04:LTS and 4 morelinux-fips, linux-aws-fips, linux-gcp-fips and 1 moreno fix listedUBUNTU-CVE-2024-2193
3 more for Ubuntu in the JSON and on Ubuntu's page.
SUSELinux Enterprise High Performance Computing 15 SP2-LTSS, Linux Enterprise Server 15 SP2-LTSS, Linux Enterprise Server for SAP Applications 15 SP2xen4.13.5_12-150200.3.93.1SUSE-SU-2024:2535-1
SUSELinux Enterprise Micro 5.1, Linux Enterprise Micro 5.2xen4.14.6_12-150300.3.69.1SUSE-SU-2024:1152-1
SUSELinux Enterprise Micro 5.3, Linux Enterprise Micro 5.4xen4.16.5_14-150400.4.52.1SUSE-SU-2024:1101-1
SUSELinux Enterprise Micro 5.5, Linux Enterprise Module for Basesystem 15 SP5, Linux Enterprise Module for Server Applications 15 SP5xen4.17.3_08-150500.3.27.1SUSE-SU-2024:1102-1
SUSELinux Enterprise Server 12 SP5, Linux Enterprise Server for SAP Applications 12 SP5, Linux Enterprise Software Development Kit 12 SP5xen4.12.4_46-3.106.1SUSE-SU-2024:1105-1
openSUSELeap 15.5xen4.17.3_08-150500.3.27.1SUSE-SU-2024:1102-1
openSUSELeap Micro 5.3, Leap Micro 5.4xen4.16.5_14-150400.4.52.1SUSE-SU-2024:1101-1
openSUSETumbleweedxen4.18.1_02-1.1openSUSE-SU-2024:13801-1
Alpinev3.16, v3.17xen4.16.5-r7ALPINE-CVE-2024-2193
Alpinev3.18xen4.17.3-r1ALPINE-CVE-2024-2193
Alpinev3.19xen4.18.0-r4ALPINE-CVE-2024-2193
Alpinev3.20, v3.21, v3.22 and 2 morexen4.18.0-r5ALPINE-CVE-2024-2193

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE · Alpine.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability poses a moderate severity issue primarily due to its potential for widespread impact across various hardware and software vendors, especially those previously affected by Spectre v1. By targeting the Linux kernel and hardware platforms supporting branch speculation, attackers exploit a race condition occurring on transiently executed paths, akin to Spectre v1, to disclose sensitive information. Unlike traditional race conditions, speculative race conditions are prevalent due to the behavior of common synchronization primitives on such paths. Although the vulnerability's exploitation has been demonstrated through a proof-of-concept exploit targeting specific patterns like speculative use-after-free for control-flow hijacking on Linux, its broader applicability underscores its significance. Exploitation follows a threat model resembling Spectre v1 but necessitates the exploitation of additional software features, such as inter-process interrupts and high-precision timers, to synchronize and enable successful attacks.

Red Hat's mitigation

There is a fix that is known as another CVE-2024-26602 and it can be considered as mitigation for this issue. It doesn't resolve this issue completely, but prevents it.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelOut of support scope
Red Hat Enterprise Linux 7kernel-rtOut of support scope
Red Hat Enterprise Linux 8kernelWill not fix
Red Hat Enterprise Linux 8kernel-rtWill not fix
Red Hat Enterprise Linux 9kernelAffected
Red Hat Enterprise Linux 9kernel-rtWill not fix

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2024-2193.

Attack patterns (CAPEC)

  • CAPEC-26 Leveraging Race Conditions Likelihood: High · Severity: High
  • CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON