CVE-2023-52636 Vulnerability Analysis & Exploit Details

CVE-2023-52636
Vulnerability Scoring

5.5
/10
Significant Risk

Security assessments indicate that CVE-2023-52636 presents a notable risk, potentially requiring prompt mitigation.

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: Low
    Some privileges are necessary to exploit the vulnerability.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2023-52636 Details

Status: Analyzed

Last updated: 🕒 17 Mar 2025, 15:13 UTC
Originally published on: 🕖 02 Apr 2024, 07:15 UTC

Time between publication and last update: 349 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

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

CVE-2023-52636 Vulnerability Summary

CVE-2023-52636: In the Linux kernel, the following vulnerability has been resolved: libceph: just wait for more data to be available on the socket A short read may occur while reading the message footer from the socket. Later, when the socket is ready for another read, the messenger invokes all read_partial_*() handlers, including read_partial_sparse_msg_data(). The expectation is that read_partial_sparse_msg_data() would bail, allowing the messenger to invoke read_partial() for the footer and pick up where it left off. However read_partial_sparse_msg_data() violates that and ends up calling into the state machine in the OSD client. The sparse-read state machine assumes that it's a new op and interprets some piece of the footer as the sparse-read header and returns bogus extents/data length, etc. To determine whether read_partial_sparse_msg_data() should bail, let's reuse cursor->total_resid. Because once it reaches to zero that means all the extents and data have been successfully received in last read, else it could break out when partially reading any of the extents and data. And then osd_sparse_read() could continue where it left off. [ idryomov: changelog ]

Assessing the Risk of CVE-2023-52636

Access Complexity Graph

The exploitability of CVE-2023-52636 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-52636

CVE-2023-52636 presents an accessible attack vector with minimal effort required. Restricting access controls and implementing security updates are critical to reducing exploitation risks.

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-52636, 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-52636, 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-52636 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: None
    CVE-2023-52636 poses no threat to data integrity.
  • Availability: None
    CVE-2023-52636 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-52636 References

External References

CWE Common Weakness Enumeration

NVD-CWE-noinfo

Vulnerable Configurations

  • 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:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.2:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.2:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.3:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.3:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.4:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.4:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.5:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.5:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.6:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.6:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.7:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.7:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.8:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.8:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.9:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.9:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.10:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.10:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.11:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.11:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.12:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.12:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.13:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.13:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.14:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.14:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.15:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.15:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.6.16:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6.16:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.7:-:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.7:-:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.7.1:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.7.1:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.7.2:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.7.2:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.7.3:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.7.3:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.7.4:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.7.4:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.8:rc1:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.8:rc1:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.8:rc2:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.8:rc2:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.8:rc3:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.8:rc3:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2023-52636: 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-2025-4432 – A flaw was found in Rust's Ring package. A panic may be triggered when overflow checking is enabled. In the QUIC protocol, this flaw allows an atta...
  • CVE-2025-46193 – SourceCodester Client Database Management System 1.0 is vulnerable to Remote code execution via Arbitrary file upload in user_proposal_update_order.php.
  • CVE-2025-46189 – SourceCodester Client Database Management System 1.0 is vulnerable to SQL Injection in user_order_customer_update.php via the order_id POST parameter.
  • CVE-2025-46188 – SourceCodester Client Database Management System 1.0 is vulnerable to SQL Injection in superadmin_phpmyadmin.php.
  • CVE-2025-45513 – Tenda FH451 V1.0.0.9 has a stack overflow vulnerability in the function.P2pListFilter.