CVE-2026-53371

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-07-19. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

July 19, 2026

Last Modified

July 29, 2026

Advisory Details (3)

Auto-updated Jul 29, 2026
No patch confirmed yet.
generic

RDMA/ionic: bound node_desc sysfs read with %.64s - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a3e9372203afde2c62576356bb9a17890bc7fd6c
generic

RDMA/ionic: bound node_desc sysfs read with %.64s - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/654a27f25530d052eeedf086e6c3e2d585c203bd
generic

RDMA/ionic: bound node_desc sysfs read with %.64s - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/61df14f306f153bffa2f3c74a94ff5a85c99fa39

Vendor Advisories for CVE-2026-53371(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(5)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.7-1~bpo13+1 (133 versions)7.0.7-1

All Vendor Advisories

(5)

Data Freshness Timeline

(refreshed 23× in last 7d / 94× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 120 total refreshes for this CVE.

  1. 2026-08-30 03:06 UTCEG score recompute
  2. 2026-08-30 03:06 UTCVendor advisory
  3. 2026-08-30 03:06 UTCGHSA enrichment
  4. 2026-08-30 01:22 UTCEPSS rescore
  5. 2026-08-28 21:41 UTCEPSS rescore
  6. 2026-08-28 01:46 UTCEG score recompute
  7. 2026-08-28 01:46 UTCVendor advisory
  8. 2026-08-28 01:46 UTCGHSA enrichment
  9. 2026-08-27 14:25 UTCEPSS rescore
  10. 2026-08-26 23:14 UTCEG score recompute
  11. 2026-08-26 23:14 UTCVendor advisory
  12. 2026-08-26 23:14 UTCGHSA enrichment
  13. 2026-08-26 14:46 UTCEPSS rescore
  14. 2026-08-25 21:12 UTCEG score recompute
  15. 2026-08-25 21:12 UTCVendor advisory
  16. 2026-08-25 21:12 UTCGHSA enrichment
  17. 2026-08-25 13:49 UTCEPSS rescore
  18. 2026-08-24 19:12 UTCEG score recompute
  19. 2026-08-24 19:12 UTCVendor advisory
  20. 2026-08-24 19:12 UTCGHSA enrichment
  21. 2026-08-23 16:34 UTCEG score recompute
  22. 2026-08-23 16:34 UTCVendor advisory
  23. 2026-08-23 16:34 UTCGHSA enrichment
  24. 2026-08-23 00:19 UTCEPSS rescore
  25. 2026-08-22 14:34 UTCVendor advisory
Show 75 more
  1. 2026-08-22 14:34 UTCGHSA enrichment
  2. 2026-08-21 12:27 UTCEG score recompute
  3. 2026-08-21 12:27 UTCVendor advisory
  4. 2026-08-21 12:27 UTCGHSA enrichment
  5. 2026-08-20 22:55 UTCEPSS rescore
  6. 2026-08-20 10:26 UTCVendor advisory
  7. 2026-08-20 10:26 UTCGHSA enrichment
  8. 2026-08-19 08:25 UTCEG score recompute
  9. 2026-08-19 08:25 UTCVendor advisory
  10. 2026-08-19 08:25 UTCGHSA enrichment
  11. 2026-08-18 13:48 UTCEPSS rescore
  12. 2026-08-18 06:24 UTCEG score recompute
  13. 2026-08-18 06:24 UTCVendor advisory
  14. 2026-08-18 06:24 UTCGHSA enrichment
  15. 2026-08-17 13:47 UTCEPSS rescore
  16. 2026-08-17 04:24 UTCEG score recompute
  17. 2026-08-17 04:24 UTCVendor advisory
  18. 2026-08-17 04:24 UTCGHSA enrichment
  19. 2026-08-16 14:56 UTCEPSS rescore
  20. 2026-08-16 02:23 UTCEG score recompute
  21. 2026-08-16 02:23 UTCVendor advisory
  22. 2026-08-16 02:23 UTCGHSA enrichment
  23. 2026-08-16 02:14 UTCEPSS rescore
  24. 2026-08-15 01:30 UTCEPSS rescore
  25. 2026-08-15 00:23 UTCVendor advisory
  26. 2026-08-15 00:23 UTCGHSA enrichment
  27. 2026-08-13 22:22 UTCEG score recompute
  28. 2026-08-13 22:22 UTCVendor advisory
  29. 2026-08-13 22:22 UTCGHSA enrichment
  30. 2026-08-13 22:00 UTCEPSS rescore
  31. 2026-08-12 20:22 UTCEG score recompute
  32. 2026-08-12 20:22 UTCVendor advisory
  33. 2026-08-12 20:22 UTCGHSA enrichment
  34. 2026-08-12 13:51 UTCEPSS rescore
  35. 2026-08-11 18:20 UTCEG score recompute
  36. 2026-08-11 18:20 UTCVendor advisory
  37. 2026-08-11 18:20 UTCGHSA enrichment
  38. 2026-08-11 00:00 UTCEPSS rescore
  39. 2026-08-10 16:11 UTCVendor advisory
  40. 2026-08-10 16:11 UTCGHSA enrichment
  41. 2026-08-09 14:10 UTCEG score recompute
  42. 2026-08-09 14:10 UTCVendor advisory
  43. 2026-08-09 14:10 UTCGHSA enrichment
  44. 2026-08-09 13:46 UTCEPSS rescore
  45. 2026-08-08 16:37 UTCEPSS rescore
  46. 2026-08-08 12:10 UTCVendor advisory
  47. 2026-08-08 12:10 UTCGHSA enrichment
  48. 2026-08-07 10:09 UTCEG score recompute
  49. 2026-08-07 10:09 UTCVendor advisory
  50. 2026-08-07 10:09 UTCGHSA enrichment
  51. 2026-08-06 13:47 UTCEPSS rescore
  52. 2026-08-06 08:08 UTCEG score recompute
  53. 2026-08-06 08:08 UTCVendor advisory
  54. 2026-08-06 08:08 UTCGHSA enrichment
  55. 2026-08-05 19:17 UTCEPSS rescore
  56. 2026-08-05 06:08 UTCEG score recompute
  57. 2026-08-05 06:08 UTCGHSA enrichment
  58. 2026-08-04 15:10 UTCEPSS rescore
  59. 2026-08-04 03:13 UTCEG score recompute
  60. 2026-08-04 03:13 UTCVendor advisory
  61. 2026-08-04 03:13 UTCGHSA enrichment
  62. 2026-08-03 10:36 UTCEPSS rescore
  63. 2026-08-03 01:12 UTCEG score recompute
  64. 2026-08-03 01:12 UTCVendor advisory
  65. 2026-08-03 01:12 UTCGHSA enrichment
  66. 2026-08-02 02:27 UTCEPSS rescore
  67. 2026-08-01 23:11 UTCVendor advisory
  68. 2026-08-01 23:11 UTCGHSA enrichment
  69. 2026-07-31 21:10 UTCGHSA enrichment
  70. 2026-07-30 19:07 UTCEG score recompute
  71. 2026-07-30 19:07 UTCVendor advisory
  72. 2026-07-30 19:07 UTCGHSA enrichment
  73. 2026-07-30 16:28 UTCEPSS rescore
  74. 2026-07-30 01:30 UTCEPSS rescore
  75. 2026-07-29 17:05 UTCEG score recompute 5.50

Frequently asked(5)

What is CVE-2026-53371?
CVE-2026-53371 is a medium vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: RDMA/ionic: bound node_desc sysfs read with %.64s nodedesc[64] in struct ibdevice 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…
When was CVE-2026-53371 disclosed?
CVE-2026-53371 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on July 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53371 actively exploited?
CVE-2026-53371 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.6% of all scored CVEs.
What is the CVSS score of CVE-2026-53371?
CVE-2026-53371 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-53371?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53371, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53371

Explore →

Is Your Infrastructure Affected by CVE-2026-53371?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.