CVE-2026-53371 Vulnerability Analysis & Exploit Details

CVE-2026-53371
Vulnerability Scoring

5.5
/10
Significant Risk

Security assessments indicate that CVE-2026-53371 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-2026-53371 Details

Status: Analyzed

Last updated: 🕟 29 Jul 2026, 16:55 UTC
Originally published on: 🕘 19 Jul 2026, 09:17 UTC

Time between publication and last update: 10 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-2026-53371 Vulnerability Summary

CVE-2026-53371: In the Linux kernel, the following vulnerability has been resolved: RDMA/ionic: bound node_desc sysfs read with %.64s node_desc[64] in struct ib_device is not guaranteed to be NUL- terminated. The core IB sysfs handler uses "%.64s" for exactly this reason (drivers/infiniband/core/sysfs.c:1307), since node_desc_store() performs a raw memcpy of up to IB_DEVICE_NODE_DESC_MAX bytes with no NUL termination: memcpy(desc.node_desc, buf, min_t(int, count, IB_DEVICE_NODE_DESC_MAX)); If exactly 64 bytes are written via the node_desc sysfs file, the array contains no NUL byte. The ionic hca_type_show() handler uses unbounded "%s" and will read past the end of node_desc into adjacent fields of struct ib_device until it encounters a NUL. ionic supports IB_DEVICE_MODIFY_NODE_DESC, so this is triggerable by userspace. Match the core handler and bound the format specifier.

Assessing the Risk of CVE-2026-53371

Access Complexity Graph

The exploitability of CVE-2026-53371 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-2026-53371

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

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

CVE-2026-53371 References

External References

CWE Common Weakness Enumeration

NVD-CWE-noinfo

Vulnerable Configurations

  • cpe:2.3:o:linux:linux_kernel:6.18:-:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18:-:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.1:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.1:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.2:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.2:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.3:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.3:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.4:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.4:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.5:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.5:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.6:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.6:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.7:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.7:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.8:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.8:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.9:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.9:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.10:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.10:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.11:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.11:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.13:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.13:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.14:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.14:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.16:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.16:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.17:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.17:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.18:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.18:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.19:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.19:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.20:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.20:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.21:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.21:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.22:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.22:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.23:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.23:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.24:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.24:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.25:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.25:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.26:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.26:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.27:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.27:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.28:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.28:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.18.29:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.18.29:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19:-:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19:-:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19.1:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19.1:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19.3:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19.3:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19.4:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19.4:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19.6:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19.6:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19.7:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19.7:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19.8:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19.8:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19.9:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19.9:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19.10:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19.10:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19.11:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19.11:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19.12:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19.12:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19.13:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19.13:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19.14:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19.14:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19:rc1:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19:rc1:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19:rc2:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19:rc2:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19:rc3:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19:rc3:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19:rc4:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19:rc4:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19:rc5:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19:rc5:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19:rc6:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19:rc6:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19:rc7:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19:rc7:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:6.19:rc8:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:6.19:rc8:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:7.0:-:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:7.0:-:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:7.0.1:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:7.0.1:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:7.0.2:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:7.0.2:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:7.0.3:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:7.0.3:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:7.0.4:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:7.0.4:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:7.0.5:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:7.0.5:*:*:*:*:*:*:*
  • cpe:2.3:o:linux:linux_kernel:7.0.6:*:*:*:*:*:*:*
    cpe:2.3:o:linux:linux_kernel:7.0.6:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2026-53371: 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-90555 – vLLM versions before 0.28.0 fail to validate audio sample rate headers in the transcription endpoint, allowing authenticated clients to bypass dura...
  • CVE-2026-90554 – vLLM versions >=0.10.2 and <0.28.0 do not apply any audio decode-size or duration limit when extracting audio from video input for NanoNemotronVL m...
  • CVE-2026-90553 – vLLM before 0.28.0 contains a remote code execution vulnerability in the LlavaOnevision2 processor loader that ignores the trust_remote_code parame...
  • CVE-2026-90552 – WWBN AVideo through commit c3edcc274c389816d434acadac07ee78eaf330c1 fails to validate playlist ownership in the Playlists_schedules/list.json.php a...
  • CVE-2026-90551 – WWBN AVideo through commit c3edcc274c389816d434acadac07ee78eaf330c1 fails to validate playlist ownership in the video_from_program API endpoint, al...