0.0
NA
CVE-2026-53371
RDMA/ionic: bound node_desc sysfs read with %.64s
Description

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.

INFO

Published Date :

July 19, 2026, 9:17 a.m.

Last Modified :

July 19, 2026, 9:17 a.m.

Remotely Exploit :

No

Source :

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

The following products are affected by CVE-2026-53371 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

No affected product recoded yet

Solution
Apply kernel patch to fix buffer overflow in sysfs handler and prevent data leaks.
  • Update the Linux kernel to the patched version.
  • Apply the specific fix for RDMA/ionic vulnerability.
  • Ensure sysfs handlers are correctly bound.
  • Verify system integrity after patching.
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2026-53371.

URL Resource
https://git.kernel.org/stable/c/61df14f306f153bffa2f3c74a94ff5a85c99fa39
https://git.kernel.org/stable/c/654a27f25530d052eeedf086e6c3e2d585c203bd
https://git.kernel.org/stable/c/a3e9372203afde2c62576356bb9a17890bc7fd6c
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-53371 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-53371 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-53371 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-53371 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Jul. 19, 2026

    Action Type Old Value New Value
    Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '2075bbe8ef03914aa2211035eec45d1d3a5c4ff2', 'lessThan': '61df14f306f153bffa2f3c74a94ff5a85c99fa39', 'versionType': 'git'}, {'status': 'affected', 'version': '2075bbe8ef03914aa2211035eec45d1d3a5c4ff2', 'lessThan': 'a3e9372203afde2c62576356bb9a17890bc7fd6c', 'versionType': 'git'}, {'status': 'affected', 'version': '2075bbe8ef03914aa2211035eec45d1d3a5c4ff2', 'lessThan': '654a27f25530d052eeedf086e6c3e2d585c203bd', 'versionType': 'git'}], 'programFiles': ['drivers/infiniband/hw/ionic/ionic_ibdev.c'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '6.18'}, {'status': 'unaffected', 'version': '0', 'lessThan': '6.18', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '6.18.30', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.0.7', 'versionType': 'semver', 'lessThanOrEqual': '7.0.*'}, {'status': 'unaffected', 'version': '7.1', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['drivers/infiniband/hw/ionic/ionic_ibdev.c'], 'defaultStatus': 'affected'}]
    Added Description 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.
    Added Reference https://git.kernel.org/stable/c/61df14f306f153bffa2f3c74a94ff5a85c99fa39
    Added Reference https://git.kernel.org/stable/c/654a27f25530d052eeedf086e6c3e2d585c203bd
    Added Reference https://git.kernel.org/stable/c/a3e9372203afde2c62576356bb9a17890bc7fd6c
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.