Skip to content
Noroxi
CVE-2024-2193· NVD / CVE Program· CNA certcc

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

Noroxi assessment

Priority: Monitor (action score 22/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 1.2% (FIRST EPSS); higher than 69.6% of all records.
  • Someone with local access to the system can trigger it. Administrator privileges are required. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: xen (Alpine:v3.16) 4.16.5-r7; xen (Alpine:v3.18) 4.17.3-r1; xen (Alpine:v3.19) 4.18.0-r4.

Low priority for now. Upgrade to xen (Alpine:v3.16) 4.16.5-r7; xen (Alpine:v3.18) 4.17.3-r1; xen (Alpine:v3.19) 4.18.0-r4 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.7 · v3.1—Proof of concept Fix available
Published
Mar 15, 2024
Updated
Jun 17, 2026
EPSS
1.2% · 69th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.7 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-2193

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (certcc). Independent of NVD's CPE analysis and usually ahead of it.

  • AMD CPU

    • See advisory AMD-SB-7016affected
  • Xen Xen

    • consult Xen advisory XSA-453affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Alpine:v3.16xenbefore 4.16.5-r74.16.5-r7
Alpine:v3.18xenbefore 4.17.3-r14.17.3-r1
Alpine:v3.19xenbefore 4.18.0-r44.18.0-r4
Alpine:v3.20xenbefore 4.18.0-r54.18.0-r5
Debian:12linuxfrom 0—
Debian:12xenbefore 4.17.5+23-ga4e5191dc0-14.17.5+23-ga4e5191dc0-1
Debian:13xenbefore 4.19.1-14.19.1-1
openSUSE:Tumbleweedxenbefore 4.18.1_02-1.14.18.1_02-1.1
SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSxenbefore 4.13.5_12-150200.3.93.14.13.5_12-150200.3.93.1
SUSE:Linux Enterprise Micro 5.1xenbefore 4.14.6_12-150300.3.69.14.14.6_12-150300.3.69.1
SUSE:Linux Enterprise Micro 5.3xenbefore 4.16.5_14-150400.4.52.14.16.5_14-150400.4.52.1
SUSE:Linux Enterprise Micro 5.3xenbefore 4.16.5_14-150400.4.52.14.16.5_14-150400.4.52.1
SUSE:Linux Enterprise Micro 5.5xenbefore 4.17.3_08-150500.3.27.14.17.3_08-150500.3.27.1
SUSE:Linux Enterprise Micro 5.5xenbefore 4.17.3_08-150500.3.27.14.17.3_08-150500.3.27.1
SUSE:Linux Enterprise Software Development Kit 12 SP5xenbefore 4.12.4_46-3.106.14.12.4_46-3.106.1

Same product

amd: all records

Other highest-scoring records for the same primary product.

  • CVE-2021-26400AMD processors may speculatively re-order load instructions which can result in stale data being observed when multiple processors are opera
    16Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
alpine:xen4.16.5-r7 · Alpine:v3.16Package registry (OSV)
debian:xen4.17.5+23-ga4e5191dc0-1 · Debian:12Package registry (OSV)
opensuse:xen4.16.5_14-150400.4.52.1 · openSUSE:Leap Micro 5.3Package registry (OSV)
suse:xen4.16.5_14-150400.4.52.1 · SUSE:Linux Enterprise Micro 5.3Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:02024-03-28

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. First PoC+12 d
  3. TodayOct 21, 2026+950 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • Administrator privileges are required.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
none
Attack vector
Local
Attack complexity
High
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
None

CVSS vector

CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records