CVE-2026-72501

UNRATEDCVSS · not yet scoredTrending — 4 sources updated this week
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

RDMA/bnxt_re: Initialize dpi variable to zero

dpi is initialized only for BNXT_RE_ALLOC_WC_PAGE, but copied for all the cases. So initialize the dpi to 0.

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.2%
EPSS %ILE
9th
KEV
Not listed

Published

August 15, 2026

Last Modified

August 17, 2026

References (3)

Vendor Advisories for CVE-2026-72501(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 / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-34.34) @ resolute2026-10-03ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1013.13~24.04.1) @ noble2026-10-03ubuntu
ubuntulinux-tools-oracle-edge (7.0.0-1012.12~24.04.1) @ noble2026-10-03ubuntu
ubuntulinux-tools-gke-hwe-26.04 (7.0.0-1007.8) @ resolute2026-10-03ubuntu

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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (181 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (160 versions)
  • every version up to 7.1.5-1: fixed in 7.1.5-1
—

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 9× in last 7d / 31× 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-10-04 23:22 UTCEPSS rescore
  2. 2026-10-03 22:43 UTCVendor advisory
  3. 2026-10-03 22:43 UTCGHSA enrichment
  4. 2026-10-03 14:26 UTCEPSS rescore
  5. 2026-10-01 19:50 UTCEPSS rescore
  6. 2026-09-30 21:02 UTCEG score recompute
  7. 2026-09-30 21:02 UTCVendor advisory
  8. 2026-09-30 21:02 UTCGHSA enrichment
  9. 2026-09-28 13:52 UTCEPSS rescore
  10. 2026-09-27 13:48 UTCEPSS rescore
  11. 2026-09-27 08:29 UTCVendor advisory
  12. 2026-09-27 08:29 UTCGHSA enrichment
  13. 2026-09-26 15:59 UTCEPSS rescore
  14. 2026-09-23 17:54 UTCEPSS rescore
  15. 2026-09-23 03:24 UTCGHSA enrichment
  16. 2026-09-21 21:09 UTCEPSS rescore
  17. 2026-09-20 20:16 UTCEPSS rescore
  18. 2026-09-20 01:50 UTCGHSA enrichment
  19. 2026-09-18 19:28 UTCEPSS rescore
  20. 2026-09-17 00:16 UTCGHSA enrichment
  21. 2026-09-16 14:08 UTCEPSS rescore
  22. 2026-09-16 05:15 UTCEPSS rescore
  23. 2026-09-15 03:12 UTCEPSS rescore
  24. 2026-09-13 22:42 UTCGHSA enrichment
  25. 2026-09-12 15:02 UTCEPSS rescore
Show 41 more
  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-10 21:08 UTCGHSA enrichment
  3. 2026-09-10 09:35 UTCEPSS rescore
  4. 2026-09-08 22:01 UTCEPSS rescore
  5. 2026-09-07 19:31 UTCGHSA enrichment
  6. 2026-09-06 13:48 UTCEPSS rescore
  7. 2026-09-04 17:56 UTCGHSA enrichment
  8. 2026-09-04 05:07 UTCEPSS rescore
  9. 2026-09-02 14:12 UTCEPSS rescore
  10. 2026-09-01 16:22 UTCGHSA enrichment
  11. 2026-09-01 13:54 UTCEPSS rescore
  12. 2026-09-01 04:40 UTCEPSS rescore
  13. 2026-09-01 04:40 UTCEPSS rescore
  14. 2026-08-30 19:18 UTCEPSS rescore
  15. 2026-08-30 19:17 UTCEPSS rescore
  16. 2026-08-30 01:22 UTCEPSS rescore
  17. 2026-08-29 14:45 UTCGHSA enrichment
  18. 2026-08-28 21:42 UTCEPSS rescore
  19. 2026-08-26 14:47 UTCEPSS rescore
  20. 2026-08-26 11:11 UTCGHSA enrichment
  21. 2026-08-25 13:49 UTCEPSS rescore
  22. 2026-08-23 09:36 UTCGHSA enrichment
  23. 2026-08-23 00:19 UTCEPSS rescore
  24. 2026-08-21 23:49 UTCEPSS rescore
  25. 2026-08-20 22:56 UTCEPSS rescore
  26. 2026-08-20 08:01 UTCGHSA enrichment
  27. 2026-08-19 17:04 UTCEPSS rescore
  28. 2026-08-18 13:49 UTCEPSS rescore
  29. 2026-08-18 13:49 UTCEPSS rescore
  30. 2026-08-17 13:47 UTCEPSS rescore
  31. 2026-08-17 06:27 UTCGHSA enrichment
  32. 2026-08-17 06:22 UTCNVD update
  33. 2026-08-17 05:28 UTCEG score recompute
  34. 2026-08-17 05:28 UTCGHSA enrichment
  35. 2026-08-17 05:24 UTCMITRE cvelistV5
  36. 2026-08-16 14:56 UTCEPSS rescore
  37. 2026-08-16 14:56 UTCEPSS rescore
  38. 2026-08-16 02:15 UTCEPSS rescore
  39. 2026-08-15 06:23 UTCNVD update
  40. 2026-08-15 06:17 UTCEG score recompute
  41. 2026-08-15 06:12 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor)

Frequently asked(4)

What is CVE-2026-72501?
CVE-2026-72501 is a publicly disclosed vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: RDMA/bnxt_re: Initialize dpi variable to zero dpi is initialized only for BNXTREALLOCWCPAGE, but copied for all the cases. So initialize the dpi to 0.
When was CVE-2026-72501 disclosed?
CVE-2026-72501 was first published on August 15, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-72501 actively exploited?
CVE-2026-72501 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (9th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-72501?
A fix for CVE-2026-72501 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-72501 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-72501

Explore →

Is Your Infrastructure Affected by CVE-2026-72501?

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

Book a Demo →Browse All CVEs