CVE-2026-53187

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-06-25. the CNA's CVSS baseline 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

RDMA/core: Validate cpu_id against nr_cpu_ids in DMAH alloc

The cpu_id attribute supplied by user space through UVERBS_ATTR_ALLOC_DMAH_CPU_ID is passed directly to cpumask_test_cpu() without first verifying that the value is within the valid CPU range.

Passing such untrusted data to cpumask_test_cpu() may lead to an out-of-bounds read of the underlying cpumask bitmap: the helper expands to a test_bit() that indexes the bitmap by cpu_id / BITS_PER_LONG with no bound check.

In addition, on kernels built with CONFIG_DEBUG_PER_CPU_MAPS it trips the WARN_ON_ONCE() in cpumask_check(); combined with panic_on_warn this turns a bad user input into a machine reboot.

Reject any cpu_id that is not smaller than nr_cpu_ids with -EINVAL before it is used.

Reported by Smatch.

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
37(Track)
EG Risk 37/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
Severity71% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

June 25, 2026

Last Modified

August 5, 2026

Advisory Details (3)

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

RDMA/core: Validate cpu_id against nr_cpu_ids in DMAH alloc - kernel/git/stable/linux.git - Linux kernel stable tree

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

RDMA/core: Validate cpu_id against nr_cpu_ids in DMAH alloc - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/323c98a4ff06aa28114f2bf658fb43eb3b536bbc
generic

RDMA/core: Validate cpu_id against nr_cpu_ids in DMAH alloc - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0efbb6b54ff56300867027d8e0800d0e32226a20

Vendor Advisories for CVE-2026-53187(1)

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

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (145 versions)7.0.13-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 63× 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 211 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-53187?
CVE-2026-53187 is a high vulnerability published on June 25, 2026. In the Linux kernel, the following vulnerability has been resolved: RDMA/core: Validate cpuid against nrcpu_ids in DMAH alloc The cpu_id attribute supplied by user space through UVERBSATTRALLOCDMAHCPUID is passed directly to cpumasktest_cpu() without first verifying that the value is within the…
When was CVE-2026-53187 disclosed?
CVE-2026-53187 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53187 actively exploited?
CVE-2026-53187 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 94.1% of all scored CVEs.
What is the CVSS score of CVE-2026-53187?
CVE-2026-53187 has a CVSS v4.0 base score of 7.1 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-53187?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53187, 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-53187

Explore →

Is Your Infrastructure Affected by CVE-2026-53187?

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

Start Free Scan →Browse All CVEs