CVE-2026-53133

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.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/umem: Fix truncation for block sizes >= 4G

When the iommu is used the linearization of the mapping can give a single block that is very large split across multiple SG entries.

When __rdma_block_iter_next() reassembles the split SG entries it is overflowing the 32 bit stack values and computed the wrong DMA addresses for blocks after the truncation.

Use the right types to hold DMA addresses.

CVSS v3
7.8
EG Score
7.8(high)
EG Risk
—
EPSS
3.0%
KEV
Not listed

Published

June 25, 2026

Last Modified

July 7, 2026

Advisory Details (8)

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

RDMA/umem: Fix truncation for block sizes >= 4G - kernel/git/stable/linux.git - Linux kernel stable tree

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

RDMA/umem: Fix truncation for block sizes >= 4G - kernel/git/stable/linux.git - Linux kernel stable tree

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

RDMA/umem: Fix truncation for block sizes >= 4G - kernel/git/stable/linux.git - Linux kernel stable tree

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

RDMA/umem: Fix truncation for block sizes >= 4G - kernel/git/stable/linux.git - Linux kernel stable tree

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

RDMA/umem: Fix truncation for block sizes >= 4G - kernel/git/stable/linux.git - Linux kernel stable tree

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

RDMA/umem: Fix truncation for block sizes >= 4G - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8fe0231adebe086c8a459c790944ac026cd99c6e
generic

RDMA/umem: Fix truncation for block sizes >= 4G - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2ff4b7817e5b78070c30f5fb5e678e452a2628b3
generic

RDMA/umem: Fix truncation for block sizes >= 4G - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/15fe76e23615f502d051ef0768f86babaf08746c

Vendor Advisories for CVE-2026-53133(2)

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 13× in last 7d / 102× 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 102 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-53133?
CVE-2026-53133 is a high vulnerability published on June 25, 2026. In the Linux kernel, the following vulnerability has been resolved: RDMA/umem: Fix truncation for block sizes >= 4G When the iommu is used the linearization of the mapping can give a single block that is very large split across multiple SG entries. When rdmablockiter_next() reassembles the split SG…
When was CVE-2026-53133 disclosed?
CVE-2026-53133 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on July 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53133 actively exploited?
CVE-2026-53133 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53133?
CVE-2026-53133 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-53133?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53133, 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-53133

Explore →

Is Your Infrastructure Affected by CVE-2026-53133?

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

Start Free Scan →Browse All CVEs