CVE-2026-93810

HIGHPre-NVD 7.07.0—
EchelonGraph scoreHIGH confidence

Score 7.0 from GitHub Security Advisory (severity: HIGH) published 2026-09-24. A secondary CVSS source baseline 7.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.0EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 7.0Exploit: 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:

cachefiles: Fix double fput

Fix a double fput() in error handling in cachefiles_create_tmpfile().

CVSS v3
7.0
EG Score
7.0HIGHhigh confidence
EG Risk
36
EG Risk 36/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
Severity70% × 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 24, 2026

Last Modified

October 3, 2026

Advisory Details (3)

Auto-updated Sep 25, 2026
No patch confirmed yet.
generic

cachefiles: Fix double fput - kernel/git/stable/linux.git - Linux kernel stable tree

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

cachefiles: Fix double fput - kernel/git/stable/linux.git - Linux kernel stable tree

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

cachefiles: Fix double fput - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/90b306eee037d0a6a8f4aac834b46e05c5ddd0bf

Vendor Advisories for CVE-2026-93810(2)

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

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (360 versions)
  • every version on: no fix on record
—
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1
  • every version up to 6.12.111-1~deb12u1: fixed in 6.12.111-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (35 versions)
  • every version up to 6.12.111-1: fixed in 6.12.111-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (179 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

(refreshed 27× in last 7d / 47× 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 01:40 UTCEG score recompute
  2. 2026-10-05 01:40 UTCGHSA enrichment
  3. 2026-10-04 23:23 UTCEPSS rescore
  4. 2026-10-04 12:57 UTCGHSA enrichment
  5. 2026-10-04 00:14 UTCEG score recompute
  6. 2026-10-04 00:14 UTCGHSA enrichment
  7. 2026-10-03 14:26 UTCEPSS rescore
  8. 2026-10-03 11:32 UTCGHSA enrichment
  9. 2026-10-02 23:52 UTCEG score recompute
  10. 2026-10-02 23:52 UTCGHSA enrichment
  11. 2026-10-02 11:06 UTCGHSA enrichment
  12. 2026-10-01 22:24 UTCEG score recompute
  13. 2026-10-01 22:23 UTCGHSA enrichment
  14. 2026-10-01 19:51 UTCEPSS rescore
  15. 2026-10-01 09:35 UTCGHSA enrichment
  16. 2026-09-30 20:52 UTCEG score recompute
  17. 2026-09-30 20:52 UTCGHSA enrichment
  18. 2026-09-30 15:04 UTCEPSS rescore
  19. 2026-09-30 08:10 UTCGHSA enrichment
  20. 2026-09-29 19:27 UTCEG score recompute
  21. 2026-09-29 19:27 UTCGHSA enrichment
  22. 2026-09-29 06:43 UTCEG score recompute
  23. 2026-09-29 06:43 UTCGHSA enrichment
  24. 2026-09-28 18:01 UTCEG score recompute
  25. 2026-09-28 18:00 UTCGHSA enrichment
Show 22 more
  1. 2026-09-28 13:52 UTCEPSS rescore
  2. 2026-09-28 13:52 UTCEPSS rescore
  3. 2026-09-28 05:01 UTCGHSA enrichment
  4. 2026-09-27 16:18 UTCEG score recompute
  5. 2026-09-27 16:18 UTCGHSA enrichment
  6. 2026-09-27 13:49 UTCEPSS rescore
  7. 2026-09-27 03:36 UTCEG score recompute
  8. 2026-09-27 03:36 UTCGHSA enrichment
  9. 2026-09-26 15:59 UTCEPSS rescore
  10. 2026-09-26 14:51 UTCGHSA enrichment
  11. 2026-09-26 02:06 UTCEG score recompute
  12. 2026-09-26 02:06 UTCGHSA enrichment
  13. 2026-09-25 13:23 UTCEG score recompute
  14. 2026-09-25 13:23 UTCGHSA enrichment
  15. 2026-09-25 12:56 UTCEG score recompute
  16. 2026-09-25 12:56 UTCGHSA enrichment
  17. 2026-09-25 05:17 UTCEG score recompute▲ 7.00
  18. 2026-09-25 05:17 UTCGHSA enrichment
  19. 2026-09-25 05:16 UTCMITRE cvelistV5CVSS v3 → 7 · severity → HIGH
  20. 2026-09-24 17:33 UTCNVD update
  21. 2026-09-24 16:30 UTCEG score recompute
  22. 2026-09-24 16:26 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-93810?
CVE-2026-93810 is a high vulnerability published on September 24, 2026. In the Linux kernel, the following vulnerability has been resolved: cachefiles: Fix double fput Fix a double fput() in error handling in cachefilescreatetmpfile().
When was CVE-2026-93810 disclosed?
CVE-2026-93810 was first published on September 24, 2026, with the most recent update on October 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-93810 actively exploited?
CVE-2026-93810 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-93810?
CVE-2026-93810 has a CVSS base score of 7.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-93810?
No fix for CVE-2026-93810 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-93810 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-93810

Explore →

Is Your Infrastructure Affected by CVE-2026-93810?

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

Book a Demo →Browse All CVEs