CVE-2023-52874 Vulnerability Analysis & Exploit Details

CVE-2023-52874
Vulnerability Scoring

7.1
/10
Very High Risk

Highly exploitable, CVE-2023-52874 poses a critical security risk that could lead to severe breaches.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Local
    Vulnerability requires local system access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Changed
    Successful exploitation can impact components beyond the vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2023-52874 Details

Status: Modified

Last updated: 🕙 04 Aug 2026, 10:18 UTC
Originally published on: 🕓 21 May 2024, 16:15 UTC

Time between publication and last update: 804 days

CVSS Release: version 3

CVSS3 Source

416baaa9-dc9f-4396-8d5f-8c081fb06d67

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2023-52874 Vulnerability Summary

CVE-2023-52874: In the Linux kernel, the following vulnerability has been resolved: x86/tdx: Zero out the missing RSI in TDX_HYPERCALL macro In the TDX_HYPERCALL asm, after the TDCALL instruction returns from the untrusted VMM, the registers that the TDX guest shares to the VMM need to be cleared to avoid speculative execution of VMM-provided values. RSI is specified in the bitmap of those registers, but it is missing when zeroing out those registers in the current TDX_HYPERCALL. It was there when it was originally added in commit 752d13305c78 ("x86/tdx: Expand __tdx_hypercall() to handle more arguments"), but was later removed in commit 1e70c680375a ("x86/tdx: Do not corrupt frame-pointer in __tdx_hypercall()"), which was correct because %rsi is later restored in the "pop %rsi". However a later commit 7a3a401874be ("x86/tdx: Drop flags from __tdx_hypercall()") removed that "pop %rsi" but forgot to add the "xor %rsi, %rsi" back. Fix by adding it back.

Assessing the Risk of CVE-2023-52874

Access Complexity Graph

The exploitability of CVE-2023-52874 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2023-52874

With low attack complexity and no required privileges, CVE-2023-52874 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2023-52874, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2023-52874, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2023-52874 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: None
    CVE-2023-52874 poses no threat to data integrity.
  • Availability: None
    CVE-2023-52874 does not impact system availability.

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 0.045% (probability of exploit)

EPSS Percentile: 18.4% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 81.6% of others.

CVE-2023-52874 References

External References

CWE Common Weakness Enumeration

NVD-CWE-Other

Vulnerable Configurations

  • cpe:2.3:o:linux:linux_kernel:6.4:-:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.4:-:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.4.1:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.4.1:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.4.2:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.4.2:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.4.3:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.4.3:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.4.4:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.4.4:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.4.5:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.4.5:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.4.6:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.4.6:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.4.7:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.4.7:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.4.8:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.4.8:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.4.9:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.4.9:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.4.10:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.4.10:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.4.11:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.4.11:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.4.12:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.4.12:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.4.13:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.4.13:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.4.14:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.4.14:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.4.15:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.4.15:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.4.16:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.4.16:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.4:rc1:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.4:rc1:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.4:rc2:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.4:rc2:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.4:rc3:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.4:rc3:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.4:rc4:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.4:rc4:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.4:rc5:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.4:rc5:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.4:rc6:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.4:rc6:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.4:rc7:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.4:rc7:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.5:-:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.5:-:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.5.1:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.5.1:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.5.2:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.5.2:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.5.3:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.5.3:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.5.4:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.5.4:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.5.5:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.5.5:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.5.6:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.5.6:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.5.7:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.5.7:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.5.8:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.5.8:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.5.9:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.5.9:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.5.10:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.5.10:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.5.11:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.5.11:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6:-:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6:-:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.1:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.1:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2023-52874: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2026-85200 – The GEO my WP plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 4.5.5.3 via the gmw_posts_locator_aj...
  • CVE-2026-85198 – The MPG – Multiple Page Generator, Bulk Landing Pages & Programmatic SEO plugin for WordPress is vulnerable to generic SQL Injection via URL Path i...
  • CVE-2026-78175 – The Tutor LMS – eLearning and online course solution plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and includin...
  • CVE-2026-78159 – The The Events Calendar plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 6.17.3 via the parse_arra...
  • CVE-2026-78006 – The The Events Calendar plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 6.17.4 via the is_safe_wi...