CVE-2026-72312

HIGHPre-NVD 7.97.9—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
7.9EG
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.9Exploit: 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: fix VF bringup affecting PF promiscuous state

Mbox handling of nix_set_rx_mode for a VF with promiscuous and all_multi flags set to false causes deletion of the PF's promiscuous and allmulti MCAM rules. This occurs because the APIs that enable/disable these rules operate only on the PF, even when the mbox request is made via a VF interface.

Guard both rvu_npc_enable_allmulti_entry() and rvu_npc_enable_promisc_entry() disable paths with an is_vf() check so that a VF bringing up or tearing down its interface cannot inadvertently clear the PF's MCAM rules.

CVSS v3
7.9
EG Score
7.9(high)
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
Severity79% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 17, 2026

Advisory Details (6)

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

octeontx2-af: fix VF bringup affecting PF promiscuous state - kernel/git/stable/linux.git - Linux kernel stable tree

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

octeontx2-af: fix VF bringup affecting PF promiscuous state - kernel/git/stable/linux.git - Linux kernel stable tree

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

octeontx2-af: fix VF bringup affecting PF promiscuous state - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/53e17d9ed779ad25870abb9c31bc294c71a2278c
generic

octeontx2-af: fix VF bringup affecting PF promiscuous state - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3de77d2f34c2bc2acaedabc2c5e0a561b85c283a
generic

octeontx2-af: fix VF bringup affecting PF promiscuous state - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3cf83432e0561aef6d7ec2664909d12d0ff0ffc1
generic

octeontx2-af: fix VF bringup affecting PF promiscuous state - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/212c59e5e416859579272288fd325148fc316109

Vendor Advisories for CVE-2026-72312(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 31× 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-08-20 22:56 UTCEPSS rescore
  2. 2026-08-20 21:15 UTCGHSA enrichment
  3. 2026-08-20 10:24 UTCGHSA enrichment
  4. 2026-08-19 23:33 UTCEG score recompute
  5. 2026-08-19 23:33 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-19 12:41 UTCGHSA enrichment
  8. 2026-08-19 01:50 UTCGHSA enrichment
  9. 2026-08-18 14:58 UTCEG score recompute
  10. 2026-08-18 14:58 UTCGHSA enrichment
  11. 2026-08-18 13:49 UTCEPSS rescore
  12. 2026-08-18 13:49 UTCEPSS rescore
  13. 2026-08-18 04:02 UTCGHSA enrichment
  14. 2026-08-17 17:11 UTCEG score recompute
  15. 2026-08-17 17:11 UTCGHSA enrichment
  16. 2026-08-17 13:47 UTCEPSS rescore
  17. 2026-08-17 06:19 UTCEG score recompute
  18. 2026-08-17 06:19 UTCGHSA enrichment
  19. 2026-08-17 05:59 UTCEG score recompute▲ 7.90
  20. 2026-08-17 05:59 UTCGHSA enrichment
  21. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 7.9 · severity → HIGH
  22. 2026-08-17 05:30 UTCEG score recompute
  23. 2026-08-17 05:30 UTCGHSA enrichment
  24. 2026-08-17 05:24 UTCMITRE cvelistV5
  25. 2026-08-16 14:56 UTCEPSS rescore
Show 6 more
  1. 2026-08-16 14:56 UTCEPSS rescore
  2. 2026-08-16 02:15 UTCEPSS rescore
  3. 2026-08-15 06:37 UTCGHSA enrichment
  4. 2026-08-15 06:23 UTCNVD update
  5. 2026-08-15 06:07 UTCEG score recompute
  6. 2026-08-15 06:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-72312?
CVE-2026-72312 is a high vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: octeontx2-af: fix VF bringup affecting PF promiscuous state Mbox handling of nixsetrx_mode for a VF with promiscuous and all_multi flags set to false causes deletion of the PF's promiscuous and allmulti MCAM rules. This occurs…
When was CVE-2026-72312 disclosed?
CVE-2026-72312 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-72312 actively exploited?
CVE-2026-72312 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.9% of all scored CVEs.
What is the CVSS score of CVE-2026-72312?
CVE-2026-72312 has a CVSS v3 base score of 7.9 (NVD).
How do I remediate CVE-2026-72312?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72312, 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-72312

Explore →

Is Your Infrastructure Affected by CVE-2026-72312?

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

Start Free Scan →Browse All CVEs