Linux Kernel RDMA Ionic sysfs.c hca_type_show node_desc out-of-bounds

Summaryinfo

A vulnerability has been found in Linux Kernel and classified as problematic. This impacts the function hca_type_show of the file drivers/infiniband/core/sysfs.c of the component RDMA Ionic. Performing a manipulation of the argument node_desc results in out-of-bounds. This vulnerability was named CVE-2026-53371. The attack needs to be approached locally. There is no available exploit.

Detailsinfo

A vulnerability was found in Linux Kernel (the affected version unknown). It has been classified as problematic. This affects the function hca_type_show of the file drivers/infiniband/core/sysfs.c of the component RDMA Ionic. The manipulation of the argument node_desc with an unknown input leads to a out-of-bounds vulnerability. CWE is classifying the issue as CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

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.

It is possible to read the advisory at git.kernel.org. This vulnerability is uniquely identified as CVE-2026-53371 since 06/09/2026. The exploitability is told to be easy. Attacking locally is a requirement. It demands that the victim is doing some kind of user interaction. Technical details of the vulnerability are known, but there is no available exploit.

Applying the patch 61df14f306f153bffa2f3c74a94ff5a85c99fa39 is able to eliminate this problem.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-45441). Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Type

• Operating System

Vendor

• Linux

Name

• Kernel

License

• open-source

Website

• Vendor: https://www.kernel.org/

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion