CVE-2026-80675

HIGHPre-NVD 7.17.1—
EchelonGraph scoreHIGH confidence

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

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

libbpf: Reject non-exclusive metadata maps in the signed loader

The loader verifies map->sha against the metadata hash in its instructions. map->sha is calculated when BPF_OBJ_GET_INFO_BY_FD is called on the frozen map.

While the map is frozen, the /signed loader/ must also ensure the map is exclusive, as, without exclusivity (which a hostile host could just omit when loading the loader), another BPF program with map access can mutate the contents afterwards, so the check passes on stale data.

With the extra check as part of the signed loader, it now refuses to move on with map->sha validation if the host set it up wrongly.

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

Published

August 28, 2026

Last Modified

August 29, 2026

Advisory Details (3)

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

libbpf: Reject non-exclusive metadata maps in the signed loader - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0fb6c9ed6493b4af01be8bb0a384574eba7df636
generic

libbpf: Reject non-exclusive metadata maps in the signed loader - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0dad5adeb34b6f78a883e8faa6a1c947a240e7c9
generic

libbpf: Reject non-exclusive metadata maps in the signed loader - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b6862b6a25c6a925fb0b0e549ee4a52a8d2966fb

Vendor Advisories for CVE-2026-80675(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 14× in last 7d / 14× 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-30 05:41 UTCEG score recompute
  2. 2026-08-30 05:41 UTCGHSA enrichment
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-29 18:35 UTCEG score recompute
  5. 2026-08-29 18:35 UTCGHSA enrichment
  6. 2026-08-29 07:26 UTCEG score recompute
  7. 2026-08-29 07:26 UTCGHSA enrichment
  8. 2026-08-29 06:36 UTCEG score recompute▲ 7.10
  9. 2026-08-29 06:36 UTCGHSA enrichment
  10. 2026-08-29 06:33 UTCMITRE cvelistV5CVSS v3 → 7.1 · severity → HIGH
  11. 2026-08-28 21:42 UTCEPSS rescore
  12. 2026-08-28 08:20 UTCNVD update
  13. 2026-08-28 07:34 UTCEG score recompute
  14. 2026-08-28 07:32 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-80675?
CVE-2026-80675 is a high vulnerability published on August 28, 2026. In the Linux kernel, the following vulnerability has been resolved: libbpf: Reject non-exclusive metadata maps in the signed loader The loader verifies map->sha against the metadata hash in its instructions. map->sha is calculated when BPFOBJGETINFOBY_FD is called on the frozen map. While the map…
When was CVE-2026-80675 disclosed?
CVE-2026-80675 was first published in the National Vulnerability Database on August 28, 2026, with the most recent update on August 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-80675 actively exploited?
CVE-2026-80675 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.6% of all scored CVEs.
What is the CVSS score of CVE-2026-80675?
CVE-2026-80675 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-80675?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-80675, 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-80675

Explore →

Is Your Infrastructure Affected by CVE-2026-80675?

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

Start Free Scan →Browse All CVEs