CVE-2023-53496 Vulnerability Analysis & Exploit Details

CVE-2023-53496
Vulnerability Scoring

5.5
/10
Significant Risk

Security assessments indicate that CVE-2023-53496 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-53496 Details

Status: Analyzed

Last updated: 🕣 16 Jan 2026, 20:47 UTC
Originally published on: 🕛 01 Oct 2025, 12:15 UTC

Time between publication and last update: 107 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:N/I:N/A:H

CVE-2023-53496 Vulnerability Summary

CVE-2023-53496: In the Linux kernel, the following vulnerability has been resolved: x86/platform/uv: Use alternate source for socket to node data The UV code attempts to build a set of tables to allow it to do bidirectional socket<=>node lookups. But when nr_cpus is set to a smaller number than actually present, the cpu_to_node() mapping information for unused CPUs is not available to build_socket_tables(). This results in skipping some nodes or sockets when creating the tables and leaving some -1's for later code to trip. over, causing oopses. The problem is that the socket<=>node lookups are created by doing a loop over all CPUs, then looking up the CPU's APICID and socket. But if a CPU is not present, there is no way to start this lookup. Instead of looping over all CPUs, take CPUs out of the equation entirely. Loop over all APICIDs which are mapped to a valid NUMA node. Then just extract the socket-id from the APICID. This avoid tripping over disabled CPUs.

Assessing the Risk of CVE-2023-53496

Access Complexity Graph

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

CVE-2023-53496 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-53496, 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-53496, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: None
    CVE-2023-53496 has no significant impact on data confidentiality.
  • Integrity: None
    CVE-2023-53496 poses no threat to data integrity.
  • Availability: High
    CVE-2023-53496 can disrupt system operations, potentially causing complete denial of service (DoS).

CVE-2023-53496 References

External References

CWE Common Weakness Enumeration

NVD-CWE-noinfo

Vulnerable Configurations

  • 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.6:rc1:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.6:rc1:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2023-53496: 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-14554 – The Sell BTC - Cryptocurrency Selling Calculator plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'orderform_data' AJAX ac...
  • CVE-2026-23039 – In the Linux kernel, the following vulnerability has been resolved: drm/gud: fix NULL fb and crtc dereferences on USB disconnect On disconnect dr...
  • CVE-2026-23038 – In the Linux kernel, the following vulnerability has been resolved: pnfs/flexfiles: Fix memory leak in nfs4_ff_alloc_deviceid_node() In nfs4_ff_a...
  • CVE-2026-23037 – In the Linux kernel, the following vulnerability has been resolved: can: etas_es58x: allow partial RX URB allocation to succeed When es58x_alloc_...
  • CVE-2026-23036 – In the Linux kernel, the following vulnerability has been resolved: btrfs: release path before iget_failed() in btrfs_read_locked_inode() In btrf...