CVE-2026-53188

HIGHPre-NVD 8.88.8
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.8Exploit: 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 the passed in fops for ib_get_ucaps()

Sashiko pointed out it is not safe to rely only on the devt because char/block alias so if the user finds a block device with the same dev_t it can masquerade as a ucap cdev fd.

Test the f_ops to only accept authentic cdevs.

CVSS v3
8.8
EG Score
8.8(high)
EPSS
3.4%
KEV
Not listed

Published

June 25, 2026

Last Modified

July 6, 2026

Advisory Details (3)

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

RDMA/core: Validate the passed in fops for ib_get_ucaps() - kernel/git/stable/linux.git - Linux kernel stable tree

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

RDMA/core: Validate the passed in fops for ib_get_ucaps() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/96b6e98ff12d50ed5817230c6f1188e1150d225d
generic

RDMA/core: Validate the passed in fops for ib_get_ucaps() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4a1b1ac2744694a2ecd66a84bdb1445f4ef24bee

Vendor Advisories for CVE-2026-53188(1)

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

Data Freshness Timeline

(refreshed 32× in last 7d / 50× 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-06 18:17 UTCEG score recompute
  2. 2026-07-06 18:17 UTCGHSA enrichment
  3. 2026-07-06 04:55 UTCEG score recompute
  4. 2026-07-06 04:55 UTCGHSA enrichment
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-06 02:23 UTCEPSS rescore
  7. 2026-07-05 15:46 UTCEG score recompute
  8. 2026-07-05 15:46 UTCGHSA enrichment
  9. 2026-07-05 02:38 UTCEG score recompute
  10. 2026-07-05 02:38 UTCGHSA enrichment
  11. 2026-07-05 02:31 UTCEPSS rescore
  12. 2026-07-05 02:30 UTCEPSS rescore
  13. 2026-07-04 13:27 UTCEG score recompute
  14. 2026-07-04 13:27 UTCGHSA enrichment
  15. 2026-07-04 06:31 UTCEPSS rescore
  16. 2026-07-04 06:31 UTCEPSS rescore
  17. 2026-07-04 00:19 UTCEG score recompute
  18. 2026-07-04 00:18 UTCGHSA enrichment
  19. 2026-07-03 11:10 UTCEG score recompute
  20. 2026-07-03 11:10 UTCGHSA enrichment
  21. 2026-07-02 22:02 UTCEG score recompute
  22. 2026-07-02 22:02 UTCGHSA enrichment
  23. 2026-07-02 08:53 UTCEG score recompute
  24. 2026-07-02 08:53 UTCGHSA enrichment
  25. 2026-07-01 19:43 UTCEG score recompute
Show 25 more
  1. 2026-07-01 19:43 UTCGHSA enrichment
  2. 2026-07-01 15:07 UTCEPSS rescore
  3. 2026-07-01 06:35 UTCEG score recompute
  4. 2026-07-01 06:35 UTCGHSA enrichment
  5. 2026-06-30 23:22 UTCEPSS rescore
  6. 2026-06-30 17:26 UTCEG score recompute
  7. 2026-06-30 17:26 UTCGHSA enrichment
  8. 2026-06-30 04:17 UTCEG score recompute
  9. 2026-06-30 04:17 UTCGHSA enrichment
  10. 2026-06-29 15:09 UTCEG score recompute
  11. 2026-06-29 15:08 UTCGHSA enrichment
  12. 2026-06-29 14:06 UTCEPSS rescore
  13. 2026-06-29 14:06 UTCEPSS rescore
  14. 2026-06-29 01:59 UTCEG score recompute
  15. 2026-06-29 01:59 UTCGHSA enrichment
  16. 2026-06-28 14:07 UTCEPSS rescore
  17. 2026-06-28 12:50 UTCEG score recompute 8.80
  18. 2026-06-28 12:50 UTCGHSA enrichment
  19. 2026-06-28 07:52 UTCMITRE cvelistV5CVSS v3 → 8.8 · severity → HIGH
  20. 2026-06-28 04:56 UTCEPSS rescore
  21. 2026-06-28 04:56 UTCEPSS rescore
  22. 2026-06-27 03:08 UTCEPSS rescore
  23. 2026-06-25 13:49 UTCEPSS rescore
  24. 2026-06-25 10:08 UTCEG score recompute
  25. 2026-06-25 10:08 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-53188?
CVE-2026-53188 is a high vulnerability published on June 25, 2026. In the Linux kernel, the following vulnerability has been resolved: RDMA/core: Validate the passed in fops for ibgetucaps() Sashiko pointed out it is not safe to rely only on the devt because char/block alias so if the user finds a block device with the same dev_t it can masquerade as a ucap cdev…
When was CVE-2026-53188 disclosed?
CVE-2026-53188 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-53188 actively exploited?
CVE-2026-53188 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53188?
CVE-2026-53188 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-53188?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53188, 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-53188

Explore →

Is Your Infrastructure Affected by CVE-2026-53188?

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