CVE Database›Document archive›CVE-2024-2193

CVE-2024-2193

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)

Loading…

Severity

Moderate

Red Hat Product Security

5.5

CVSS 3.1

Review impact separately from score.

Published · March 12, 2024

Updated · October 27, 2026

Description

A new cache speculation vulnerability, known as Spectre-SRC (Speculative Race Conditions), was found in hw. Spectre-SRC is similar to the Spectre v1 and allows speculative use-after-free. The difference between this issue and Spectre V1 is that this issue is based on synchronization primitives with the possibility to bypass software features such as IPIs and high-precision timers, which may disclose arbitrary data from a privileged component that should not be accessible.

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.

CVSS score applicability

The CVSS score(s) listed for this vulnerability do not reflect the associated product's status, and are included for informational purposes to better understand the severity of this vulnerability.

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.

CVSS / CWE

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

CWE-1300 · Improper Protection of Physical Side Channels