CVE-2026-93816

HIGHPre-NVD 7.17.1—
EchelonGraph scoreHIGH confidence

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

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

f2fs: validate inline dentry name lengths before conversion

Inline dentry conversion copies names out of the inline dentry area before checking that each recorded name length fits in the available filename slots.

A corrupted image can therefore make the conversion path read past the inline filename storage while building the regular dentry block.

Validate each inline dentry name length against the inline filename area before copying it.

CVSS v3
7.1
EG Score
7.1HIGHhigh confidence
EG Risk
37
EG Risk 37/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
Severity71% × 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
2nd
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

f2fs: validate inline dentry name lengths before conversion - kernel/git/stable/linux.git - Linux kernel stable tree

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

f2fs: validate inline dentry name lengths before conversion - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7caa8a0ae94b132576c2e46e9b4fd4e0f356f373
generic

f2fs: validate inline dentry name lengths before conversion - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2ce0bc5853bec7cdc724477a87ea579fde664243

Vendor Advisories for CVE-2026-93816(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 46× in last 7d / 68× 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 07:07 UTCEG score recompute
  2. 2026-10-05 07:07 UTCVendor advisory
  3. 2026-10-05 07:07 UTCGHSA enrichment
  4. 2026-10-04 23:23 UTCEPSS rescore
  5. 2026-10-04 20:15 UTCVendor advisory
  6. 2026-10-04 20:14 UTCGHSA enrichment
  7. 2026-10-04 09:18 UTCVendor advisory
  8. 2026-10-04 09:18 UTCGHSA enrichment
  9. 2026-10-03 22:26 UTCEG score recompute
  10. 2026-10-03 22:26 UTCVendor advisory
  11. 2026-10-03 22:25 UTCGHSA enrichment
  12. 2026-10-03 14:26 UTCEPSS rescore
  13. 2026-10-03 11:32 UTCVendor advisory
  14. 2026-10-03 11:32 UTCGHSA enrichment
  15. 2026-10-03 06:47 UTCVendor advisory
  16. 2026-10-03 06:47 UTCGHSA enrichment
  17. 2026-10-02 19:55 UTCEG score recompute
  18. 2026-10-02 19:55 UTCVendor advisory
  19. 2026-10-02 19:55 UTCGHSA enrichment
  20. 2026-10-02 09:03 UTCVendor advisory
  21. 2026-10-02 09:03 UTCGHSA enrichment
  22. 2026-10-01 22:12 UTCEG score recompute
  23. 2026-10-01 22:12 UTCVendor advisory
  24. 2026-10-01 22:11 UTCGHSA enrichment
  25. 2026-10-01 19:51 UTCEPSS rescore
Show 43 more
  1. 2026-10-01 11:16 UTCVendor advisory
  2. 2026-10-01 11:16 UTCGHSA enrichment
  3. 2026-10-01 00:25 UTCEG score recompute
  4. 2026-10-01 00:25 UTCVendor advisory
  5. 2026-10-01 00:25 UTCGHSA enrichment
  6. 2026-09-30 15:04 UTCEPSS rescore
  7. 2026-09-30 13:32 UTCVendor advisory
  8. 2026-09-30 13:32 UTCGHSA enrichment
  9. 2026-09-30 02:40 UTCVendor advisory
  10. 2026-09-30 02:40 UTCGHSA enrichment
  11. 2026-09-29 15:49 UTCEG score recompute
  12. 2026-09-29 15:49 UTCVendor advisory
  13. 2026-09-29 15:49 UTCGHSA enrichment
  14. 2026-09-29 04:52 UTCEG score recompute
  15. 2026-09-29 04:52 UTCVendor advisory
  16. 2026-09-29 04:52 UTCGHSA enrichment
  17. 2026-09-28 18:01 UTCEG score recompute
  18. 2026-09-28 18:01 UTCVendor advisory
  19. 2026-09-28 18:00 UTCGHSA enrichment
  20. 2026-09-28 13:52 UTCEPSS rescore
  21. 2026-09-28 13:52 UTCEPSS rescore
  22. 2026-09-28 07:05 UTCVendor advisory
  23. 2026-09-28 07:05 UTCGHSA enrichment
  24. 2026-09-27 20:14 UTCEG score recompute
  25. 2026-09-27 20:14 UTCGHSA enrichment
  26. 2026-09-27 13:49 UTCEPSS rescore
  27. 2026-09-27 09:22 UTCGHSA enrichment
  28. 2026-09-26 22:31 UTCEG score recompute
  29. 2026-09-26 22:31 UTCGHSA enrichment
  30. 2026-09-26 15:59 UTCEPSS rescore
  31. 2026-09-26 11:35 UTCGHSA enrichment
  32. 2026-09-26 00:44 UTCEG score recompute
  33. 2026-09-26 00:43 UTCGHSA enrichment
  34. 2026-09-25 13:23 UTCEG score recompute
  35. 2026-09-25 13:22 UTCGHSA enrichment
  36. 2026-09-25 12:56 UTCEG score recompute
  37. 2026-09-25 12:56 UTCGHSA enrichment
  38. 2026-09-25 05:17 UTCEG score recompute▲ 7.10
  39. 2026-09-25 05:17 UTCGHSA enrichment
  40. 2026-09-25 05:16 UTCMITRE cvelistV5CVSS v3 → 7.1 · severity → HIGH
  41. 2026-09-24 17:33 UTCNVD update
  42. 2026-09-24 16:30 UTCEG score recompute
  43. 2026-09-24 16:26 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-93816?
CVE-2026-93816 is a high vulnerability published on September 24, 2026. In the Linux kernel, the following vulnerability has been resolved: f2fs: validate inline dentry name lengths before conversion Inline dentry conversion copies names out of the inline dentry area before checking that each recorded name length fits in the available filename slots. A corrupted image…
When was CVE-2026-93816 disclosed?
CVE-2026-93816 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-93816 actively exploited?
CVE-2026-93816 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-93816?
CVE-2026-93816 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-93816?
No fix for CVE-2026-93816 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-93816 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-93816

Explore →

Is Your Infrastructure Affected by CVE-2026-93816?

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