Skip to content
Fencer Vulns
medium 5.7

CVE-2024-2193 json

Speculative Race Condition impacts modern CPU architectures that support speculative execution, also known as GhostRace.

published 2024-03-15 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-27155

cvss
5.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.3%
EPSS 1.3% chance of exploitation in 30 days, percentile 70%
public exploits
0
none known

Summary

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.

Patch / fix

  • xen Debian 12 4.17.5+23-ga4e5191dc0-1
  • xen Debian 14, Debian 13 4.19.1-1

debian advisories DEBIAN-CVE-2024-2193

  • xen SLE Micro 5.2, SLE Micro 5.1 4.14.6_12-150300.3.69.1
  • xen SLES for SAP 12 SP5, SLES 12 SP5, SLE Software Development Kit 12 SP5 4.12.4_46-3.106.1
  • xen SLE Module for Server Applications 15 SP5, SLE Module for Basesystem 15 SP5, SLE Micro 5.5 +1 more 4.17.3_08-150500.3.27.1
  • xen SLE Micro 5.4, SLE Micro 5.3, openSUSE Leap Micro 5.4 +1 more 4.16.5_14-150400.4.52.1
  • xen SLES for SAP 15 SP2, SLES 15 SP2-LTSS, SLE High Performance Computing 15 SP2-LTSS 4.13.5_12-150200.3.93.1

suse advisories SUSE-SU-2024:2535-1SUSE-SU-2024:1152-1SUSE-SU-2024:1105-1SUSE-SU-2024:1102-1SUSE-SU-2024:1101-1

  • xen openSUSE Tumbleweed 4.18.1_02-1.1

opensuse advisories openSUSE-SU-2024:13801-1

  • xen Alpine 3.17, Alpine 3.16 4.16.5-r7
  • xen Alpine 3.18 4.17.3-r1
  • xen Alpine 3.19 4.18.0-r4
  • xen Alpine 3.24, Alpine 3.23, Alpine 3.22 +2 more 4.18.0-r5

alpine advisories ALPINE-CVE-2024-2193

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2024-2193 updated cvss 5.5

hw: Spectre-SRC that is Speculative Race Conditions (SRCs) for synchronization primitives similar like Spectre V1 with possibility to bypass software features (e.g., IPIs, high-precision timers, etc)

  • Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more
    affected: workaround, no fix planned “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.”
  • Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more
    affected: workaround, no fix available, no fix planned “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.”
  • Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2 y ago

Exploit prediction

1.28% chance of exploitation in the next 30 days, higher than 70% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CISA ADP 3.1 5.7 CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N
CNA 3.1 5.7 CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N

Affected products

  • AMD CPU
  • Xen Xen

Classification

Weakness
  • CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.