CVE-2026-53133

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 4 sources updated this week
7.8EG
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.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

Published

June 25, 2026

Last Modified

August 5, 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.

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-oem-7.0 (7.0.0-1013.13) @ resolute2026-09-18ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-18ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-31.31) @ resolute2026-09-18ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1018.18~24.04.1) @ noble2026-09-18ubuntu

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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)5.10.259-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1—
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.

Additional Vendor Advisories

(4)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 15× in last 7d / 58× 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 296 total refreshes for this CVE.

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

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 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-53133 actively exploited?
CVE-2026-53133 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.1% of all scored CVEs.
What is the CVSS score of CVE-2026-53133?
CVE-2026-53133 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
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

See which npm, PyPI, Go, and Maven packages are affected by 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