CVE-2026-100079

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:

usb: typec: ucsi: unregister debugfs entries on teardown

ucsi_register() creates per-instance debugfs entries, but ucsi_unregister() keeps them around until ucsi_destroy().

Drivers like ucsi_glink that unregister/register the same UCSI instance across remoteproc restart then try to create an already existing debugfs directory and log:

debugfs: 'pmic_glink.ucsi.0' already exists in 'ucsi'

Unregister debugfs entries as part of ucsi_unregister(), and clear ucsi->debugfs after freeing it so repeated unregister paths remain safe.

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 (5)

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

usb: typec: ucsi: unregister debugfs entries on teardown - kernel/git/stable/linux.git - Linux kernel stable tree

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

usb: typec: ucsi: unregister debugfs entries on teardown - kernel/git/stable/linux.git - Linux kernel stable tree

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

usb: typec: ucsi: unregister debugfs entries on teardown - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7177c215e69658adbd2f2fc5b72e14be9208d2ba
generic

usb: typec: ucsi: unregister debugfs entries on teardown - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/62efee351566321ad72a4abaf6eb7d972590585d
generic

usb: typec: ucsi: unregister debugfs entries on teardown - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1f44d001620fd3caa30619a9bc73e9d15555408b

Vendor Advisories for CVE-2026-100079(2)

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

Weakness Classification(1)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-100079?
CVE-2026-100079 is a medium vulnerability published on September 25, 2026. In the Linux kernel, the following vulnerability has been resolved: usb: typec: ucsi: unregister debugfs entries on teardown ucsi_register() creates per-instance debugfs entries, but ucsiunregister() keeps them around until ucsidestroy(). Drivers like ucsi_glink that unregister/register the same…
When was CVE-2026-100079 disclosed?
CVE-2026-100079 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-100079 actively exploited?
CVE-2026-100079 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-100079?
CVE-2026-100079 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-100079?
No fix for CVE-2026-100079 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-100079 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-100079

Explore →

Is Your Infrastructure Affected by CVE-2026-100079?

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