CVE-2026-53187

HIGHPre-NVD 7.17.1—
EchelonGraph scoreHIGH confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-06-25. a secondary CVSS source baseline 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.1Exploit: NoneExposed: 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(high)
EPSS
2.9%
KEV
Not listed

Published

June 25, 2026

Last Modified

July 6, 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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 35× in last 7d / 53× 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.

  1. 2026-07-07 01:16 UTCEG score recompute
  2. 2026-07-07 01:16 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 13:19 UTCEG score recompute
  6. 2026-07-06 13:19 UTCGHSA enrichment
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-06 01:12 UTCEG score recompute
  10. 2026-07-06 01:12 UTCGHSA enrichment
  11. 2026-07-05 13:14 UTCEG score recompute
  12. 2026-07-05 13:14 UTCGHSA enrichment
  13. 2026-07-05 01:15 UTCEG score recompute
  14. 2026-07-05 01:15 UTCGHSA enrichment
  15. 2026-07-04 12:59 UTCEG score recompute
  16. 2026-07-04 12:59 UTCGHSA enrichment
  17. 2026-07-04 06:31 UTCEPSS rescore
  18. 2026-07-04 06:31 UTCEPSS rescore
  19. 2026-07-04 01:02 UTCEG score recompute
  20. 2026-07-04 01:02 UTCGHSA enrichment
  21. 2026-07-03 13:03 UTCEG score recompute
  22. 2026-07-03 13:03 UTCGHSA enrichment
  23. 2026-07-03 01:05 UTCEG score recompute
  24. 2026-07-03 01:05 UTCGHSA enrichment
  25. 2026-07-02 13:08 UTCEG score recompute
Show 28 more
  1. 2026-07-02 13:07 UTCGHSA enrichment
  2. 2026-07-02 01:07 UTCEG score recompute
  3. 2026-07-02 01:07 UTCGHSA enrichment
  4. 2026-07-01 13:10 UTCEG score recompute
  5. 2026-07-01 13:10 UTCGHSA enrichment
  6. 2026-07-01 01:12 UTCEG score recompute
  7. 2026-07-01 01:12 UTCGHSA enrichment
  8. 2026-06-30 23:22 UTCEPSS rescore
  9. 2026-06-30 13:15 UTCEG score recompute
  10. 2026-06-30 13:15 UTCGHSA enrichment
  11. 2026-06-30 01:15 UTCEG score recompute
  12. 2026-06-30 01:15 UTCGHSA enrichment
  13. 2026-06-29 14:06 UTCEPSS rescore
  14. 2026-06-29 14:06 UTCEPSS rescore
  15. 2026-06-29 13:17 UTCEG score recompute
  16. 2026-06-29 13:17 UTCGHSA enrichment
  17. 2026-06-29 01:20 UTCEG score recompute
  18. 2026-06-29 01:20 UTCGHSA enrichment
  19. 2026-06-28 14:07 UTCEPSS rescore
  20. 2026-06-28 13:23 UTCEG score recompute▲ 7.10
  21. 2026-06-28 13:22 UTCGHSA enrichment
  22. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 7.1 · severity → HIGH
  23. 2026-06-28 04:56 UTCEPSS rescore
  24. 2026-06-28 04:56 UTCEPSS rescore
  25. 2026-06-27 03:08 UTCEPSS rescore
  26. 2026-06-25 13:49 UTCEPSS rescore
  27. 2026-06-25 10:08 UTCEG score recompute
  28. 2026-06-25 10:08 UTCGHSA enrichment

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 July 6, 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 2.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53187?
CVE-2026-53187 has a CVSS v3 base score of 7.1 (NVD).
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

Explore the affected products and dependency analysis for 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