CVE-2026-53371
Last modified
CVE-2026-53371 is a vulnerability of currently unknown severity. 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. EPSS estimates a 0.15% chance of exploitation in the next 30 days.
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.
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 2075bbe8ef03914aa2211035eec45d1d3a5c4ff2, < 61df14f306f153bffa2f3c74a94ff5a85c99fa39; >= 2075bbe8ef03914aa2211035eec45d1d3a5c4ff2, < a3e9372203afde2c62576356bb9a17890bc7fd6c; >= 2075bbe8ef03914aa2211035eec45d1d3a5c4ff2, < 654a27f25530d052eeedf086e6c3e2d585c203bd |
| Linux | Linux | 6.18 |
References
Timeline
- Published
- Last Modified
- Status
- Awaiting Analysis
Frequently Asked Questions
What is CVE-2026-53371?
How severe is CVE-2026-53371?
How do I fix CVE-2026-53371?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-53366In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53367In the Linux kernel, the following vulnerability has been re…
- CVE-2026-53368In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-53369In the Linux kernel, the following vulnerability has been re…8.4
- CVE-2026-5337During the analysis, it was identified that authenticated at…6.5
- CVE-2026-53370In the Linux kernel, the following vulnerability has been re…
- CVE-2026-53372In the Linux kernel, the following vulnerability has been re…
- CVE-2026-53373In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53374In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-53375In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-53376In the Linux kernel, the following vulnerability has been re…
- CVE-2026-53377In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-53371?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
