CVE-2026-72045

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
8.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: 8.8Exploit: None knownExposed: 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:

octeontx2-af: cn10k: restrict VF LMTLINE sharing to its own PF

rvu_mbox_handler_lmtst_tbl_setup() uses req->base_pcifunc as a direct index into the LMT map table to read another function's LMTLINE physical base address and copy it into the caller's own LMT map table entry. The mailbox dispatcher authenticates req->hdr.pcifunc from the IRQ source, but req->base_pcifunc is a separate payload field and is not sanitized.

Reject the request with -EPERM when a VF caller's base_pcifunc is not a valid function under its own PF. is_pf_func_valid() bounds the FUNC field to the PF's configured VF count, keeping the computed index inside the caller's own slot block.

CVSS v3
8.8
EG Score
8.8(high)
EG Risk
44(Track)
EG Risk 44/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
Severity88% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 17, 2026

Advisory Details (5)

Auto-updated Aug 17, 2026
No patch confirmed yet.
generic

octeontx2-af: cn10k: restrict VF LMTLINE sharing to its own PF - kernel/git/stable/linux.git - Linux kernel stable tree

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

octeontx2-af: cn10k: restrict VF LMTLINE sharing to its own PF - kernel/git/stable/linux.git - Linux kernel stable tree

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

octeontx2-af: cn10k: restrict VF LMTLINE sharing to its own PF - kernel/git/stable/linux.git - Linux kernel stable tree

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

octeontx2-af: cn10k: restrict VF LMTLINE sharing to its own PF - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/59da37fee81a8d76079313348ca13c5bc90dd6ae
generic

octeontx2-af: cn10k: restrict VF LMTLINE sharing to its own PF - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/54535692bec9ef464adc714108eb19e49e38b5a2

Vendor Advisories for CVE-2026-72045(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 / 32× 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-08-21 08:06 UTCEG score recompute
  2. 2026-08-21 08:06 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 19:57 UTCGHSA enrichment
  5. 2026-08-20 07:48 UTCGHSA enrichment
  6. 2026-08-19 19:40 UTCEG score recompute
  7. 2026-08-19 19:40 UTCGHSA enrichment
  8. 2026-08-19 17:04 UTCEPSS rescore
  9. 2026-08-19 07:31 UTCGHSA enrichment
  10. 2026-08-18 19:20 UTCEG score recompute
  11. 2026-08-18 19:20 UTCGHSA enrichment
  12. 2026-08-18 13:49 UTCEPSS rescore
  13. 2026-08-18 13:49 UTCEPSS rescore
  14. 2026-08-18 07:11 UTCGHSA enrichment
  15. 2026-08-17 19:02 UTCEG score recompute
  16. 2026-08-17 19:02 UTCGHSA enrichment
  17. 2026-08-17 13:47 UTCEPSS rescore
  18. 2026-08-17 06:22 UTCEG score recompute
  19. 2026-08-17 06:22 UTCGHSA enrichment
  20. 2026-08-17 06:01 UTCEG score recompute▲ 8.80
  21. 2026-08-17 06:01 UTCGHSA enrichment
  22. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 8.8 · severity → HIGH
  23. 2026-08-17 05:34 UTCEG score recompute
  24. 2026-08-17 05:34 UTCGHSA enrichment
  25. 2026-08-17 05:24 UTCMITRE cvelistV5
Show 7 more
  1. 2026-08-16 14:56 UTCEPSS rescore
  2. 2026-08-16 14:56 UTCEPSS rescore
  3. 2026-08-16 02:15 UTCEPSS rescore
  4. 2026-08-15 06:45 UTCGHSA enrichment
  5. 2026-08-15 06:23 UTCNVD update
  6. 2026-08-15 06:19 UTCEG score recompute
  7. 2026-08-15 06:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-72045?
CVE-2026-72045 is a high vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: octeontx2-af: cn10k: restrict VF LMTLINE sharing to its own PF rvumboxhandlerlmtsttblsetup() uses req->basepcifunc as a direct index into the LMT map table to read another function's LMTLINE physical base address and copy it into…
When was CVE-2026-72045 disclosed?
CVE-2026-72045 was first published in the National Vulnerability Database 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-72045 actively exploited?
CVE-2026-72045 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 94.0% of all scored CVEs.
What is the CVSS score of CVE-2026-72045?
CVE-2026-72045 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-72045?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72045, 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-72045

Explore →

Is Your Infrastructure Affected by CVE-2026-72045?

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

Start Free Scan →Browse All CVEs