CVE-2026-100077

MEDIUMNVD 5.55.5—
EchelonGraph scoreHIGH confidence

Score 5.5 from GitHub Security Advisory published 2026-09-25. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 5 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 5.5Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

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

drm/msm: Recover HW before retire hung submit

During recovery, it is not safe to retire the hung submit before we recover the GPU. Retiring the submit triggers BO free and that can result in GPU pagefaults since the GPU may be actively accessing those BOs.

To fix this, retire the submits after gpu recovery is complete in recover_worker().

Patchwork: https://patchwork.freedesktop.org/patch/730655/

CVSS v3
5.5
EG Score
5.5MEDIUMhigh confidence
EG Risk
29
EG Risk 29/100CISA SSVC

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
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.1%
EPSS %ILE
1st
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 25, 2026

Last Modified

October 2, 2026

Advisory Details (3)

Auto-updated Oct 2, 2026
No patch confirmed yet.
generic

drm/msm: Recover HW before retire hung submit - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/msm: Recover HW before retire hung submit - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/msm: Recover HW before retire hung submit - kernel/git/stable/linux.git - Linux kernel stable tree

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

Vendor Advisories for CVE-2026-100077(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (358 versions)
  • every version on: no fix on record
—
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.2~rc7-1~exp1 (178 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 25× in last 7d / 29× 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-05 08:42 UTCEG score recompute
  2. 2026-10-05 08:42 UTCVendor advisory
  3. 2026-10-05 08:42 UTCGHSA enrichment
  4. 2026-10-04 23:21 UTCEPSS rescore
  5. 2026-10-04 10:51 UTCEG score recompute
  6. 2026-10-04 10:51 UTCVendor advisory
  7. 2026-10-04 10:51 UTCGHSA enrichment
  8. 2026-10-03 14:25 UTCEPSS rescore
  9. 2026-10-03 12:57 UTCEG score recompute
  10. 2026-10-03 12:57 UTCVendor advisory
  11. 2026-10-03 12:57 UTCGHSA enrichment
  12. 2026-10-02 15:05 UTCEG score recompute▲ 5.50
  13. 2026-10-02 15:05 UTCVendor advisory
  14. 2026-10-02 15:05 UTCGHSA enrichment
  15. 2026-10-02 15:05 UTCNVD updateCVSS v3 → 5.5 · severity → MEDIUM
  16. 2026-10-01 19:49 UTCEPSS rescore
  17. 2026-09-30 15:02 UTCEPSS rescore
  18. 2026-09-30 14:32 UTCEG score recompute
  19. 2026-09-30 14:32 UTCVendor advisory
  20. 2026-09-30 14:32 UTCGHSA enrichment
  21. 2026-09-29 15:20 UTCEPSS rescore
  22. 2026-09-28 14:18 UTCEG score recompute
  23. 2026-09-28 14:18 UTCVendor advisory
  24. 2026-09-28 14:18 UTCGHSA enrichment
  25. 2026-09-28 13:50 UTCEPSS rescore
Show 4 more
  1. 2026-09-26 15:58 UTCEPSS rescore
  2. 2026-09-25 14:20 UTCNVD update
  3. 2026-09-25 13:19 UTCEG score recompute
  4. 2026-09-25 13:19 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-100077?
CVE-2026-100077 is a medium vulnerability published on September 25, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/msm: Recover HW before retire hung submit During recovery, it is not safe to retire the hung submit before we recover the GPU. Retiring the submit triggers BO free and that can result in GPU pagefaults since the GPU may be…
When was CVE-2026-100077 disclosed?
CVE-2026-100077 was first published on September 25, 2026, with the most recent update on October 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-100077 actively exploited?
CVE-2026-100077 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-100077?
CVE-2026-100077 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-100077?
No fix for CVE-2026-100077 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-100077 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-100077

Explore →

Is Your Infrastructure Affected by CVE-2026-100077?

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