CVE-2026-97437

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:

ntfs3: fix out-of-bounds read in ntfs_dir_emit() and hdr_find_e()

The bounds check in ntfs_dir_emit() compares fname->name_len (a character count) against e->size (a byte count) without accounting for the 2-byte-per-character UTF-16LE encoding or the ATTR_FILE_NAME header size:

if (fname->name_len + sizeof(struct NTFS_DE) > le16_to_cpu(e->size))

This computes: name_len + 16 > e_size

The correct check must account for the ATTR_FILE_NAME header (66 bytes before the name) and the UTF-16LE character size (2 bytes each):

sizeof(NTFS_DE) + offsetof(ATTR_FILE_NAME, name) + name_len * sizeof(short) > e_size

Which computes: 16 + 66 + name_len * 2 > e_size

The correct calculation already exists as fname_full_size() in ntfs.h and is used in cmp_fnames(), namei.c, and fslog.c, but was not used in the readdir path.

A crafted NTFS image with an index entry containing a small e->size but large fname->name_len bypasses the current check, causing ntfs_utf16_to_nls() to read past the entry boundary.

Additionally, add a key_size validation in hdr_find_e() to ensure the declared key_size does not exceed the available entry data, preventing comparison functions from reading past entry boundaries on the lookup path.

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

ntfs3: fix out-of-bounds read in ntfs_dir_emit() and hdr_find_e() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ntfs3: fix out-of-bounds read in ntfs_dir_emit() and hdr_find_e() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ntfs3: fix out-of-bounds read in ntfs_dir_emit() and hdr_find_e() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6a8149a20e46086c756c2a9202e377c0b649a0c3

Vendor Advisories for CVE-2026-97437(1)

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
—

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-97437?
CVE-2026-97437 is a high vulnerability published on September 24, 2026. In the Linux kernel, the following vulnerability has been resolved: ntfs3: fix out-of-bounds read in ntfsdiremit() and hdrfinde() The bounds check in ntfsdiremit() compares fname->name_len (a character count) against e->size (a byte count) without accounting for the 2-byte-per-character UTF-16LE…
When was CVE-2026-97437 disclosed?
CVE-2026-97437 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-97437 actively exploited?
CVE-2026-97437 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-97437?
CVE-2026-97437 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-97437?
No fix for CVE-2026-97437 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-97437 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-97437

Explore →

Is Your Infrastructure Affected by CVE-2026-97437?

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

Book a Demo →Browse All CVEs