CVE-2026-89779

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreHIGH confidence

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

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

fs/ntfs3: validate ef->size covers the record's name and value

When an EA record has a non-zero ef->size, ntfs_read_ea() only checks that the record fits in the remaining buffer (ea_size > bytes), not that ef->size is large enough to hold the record's own name_len + 1 + elength.

A crafted image can pass validation with, e.g., ef->size = 24 but elength = 0xffff. ntfs_get_ea() then trusts elength and copies it out of the undersized record, reading past the kmalloc(info->size) allocation and leaking heap memory to userspace via getxattr():

BUG: KASAN: slab-out-of-bounds in ntfs_get_ea (fs/ntfs3/xattr.c:302) Read of size 65535 at addr ffff888100794550 by task exploit __asan_memcpy (mm/kasan/shadow.c:105) ntfs_get_ea (fs/ntfs3/xattr.c:302) ntfs_getxattr (fs/ntfs3/xattr.c:848) __vfs_getxattr (fs/xattr.c:441) vfs_getxattr (fs/xattr.c:474) do_getxattr (fs/xattr.c:800) path_getxattrat (fs/xattr.c:868) do_syscall_64 (arch/x86/entry/syscall_64.c:94)

The buggy address is located 80 bytes inside of allocated 84-byte region in cache kmalloc-96

Compute the size the record needs and require ef->size to cover it.

CVSS v3
9.1
EG Score
9.1CRITICALhigh confidence
EG Risk
46
EG Risk 46/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
Severity91% × 45%
Exploitation1% × 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.7%
EPSS %ILE
52nd
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 total (CVSS ≥ 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 16, 2026

Last Modified

September 16, 2026

Advisory Details (7)

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

fs/ntfs3: validate ef->size covers the record's name and value - kernel/git/stable/linux.git - Linux kernel stable tree

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

fs/ntfs3: validate ef->size covers the record's name and value - kernel/git/stable/linux.git - Linux kernel stable tree

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

fs/ntfs3: validate ef->size covers the record's name and value - kernel/git/stable/linux.git - Linux kernel stable tree

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

fs/ntfs3: validate ef->size covers the record's name and value - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/077df8464cf24f8ffc82fb6efec2ae600686e699
generic

fs/ntfs3: validate ef->size covers the record's name and value - kernel/git/stable/linux.git - Linux kernel stable tree

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

fs/ntfs3: validate ef->size covers the record's name and value - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/28a924c7e67e6d71abeb04860b61166fecb027fc
generic

fs/ntfs3: validate ef->size covers the record's name and value - kernel/git/stable/linux.git - Linux kernel stable tree

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

Vendor Advisories for CVE-2026-89779(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 100× in last 7d / 276× 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.

Showing the most recent 100 of 276 total refreshes for this CVE.

  1. 2026-10-05 06:10 UTCVendor advisory
  2. 2026-10-05 06:10 UTCGHSA enrichment
  3. 2026-10-05 02:28 UTCEG score recompute
  4. 2026-10-05 02:28 UTCVendor advisory
  5. 2026-10-05 02:28 UTCGHSA enrichment
  6. 2026-10-04 23:22 UTCEPSS rescore
  7. 2026-10-04 22:47 UTCGHSA enrichment
  8. 2026-10-04 19:06 UTCVendor advisory
  9. 2026-10-04 19:06 UTCGHSA enrichment
  10. 2026-10-04 14:53 UTCVendor advisory
  11. 2026-10-04 14:53 UTCGHSA enrichment
  12. 2026-10-04 11:11 UTCVendor advisory
  13. 2026-10-04 11:11 UTCGHSA enrichment
  14. 2026-10-04 07:30 UTCVendor advisory
  15. 2026-10-04 07:30 UTCGHSA enrichment
  16. 2026-10-04 03:49 UTCVendor advisory
  17. 2026-10-04 03:49 UTCGHSA enrichment
  18. 2026-10-04 00:09 UTCVendor advisory
  19. 2026-10-04 00:08 UTCGHSA enrichment
  20. 2026-10-03 20:27 UTCVendor advisory
  21. 2026-10-03 20:27 UTCGHSA enrichment
  22. 2026-10-03 16:46 UTCEG score recompute
  23. 2026-10-03 16:46 UTCVendor advisory
  24. 2026-10-03 16:46 UTCGHSA enrichment
  25. 2026-10-03 13:05 UTCVendor advisory
Show 75 more
  1. 2026-10-03 13:05 UTCGHSA enrichment
  2. 2026-10-03 09:20 UTCVendor advisory
  3. 2026-10-03 09:19 UTCGHSA enrichment
  4. 2026-10-03 05:23 UTCVendor advisory
  5. 2026-10-03 05:23 UTCGHSA enrichment
  6. 2026-10-03 01:41 UTCVendor advisory
  7. 2026-10-03 01:41 UTCGHSA enrichment
  8. 2026-10-02 22:00 UTCVendor advisory
  9. 2026-10-02 22:00 UTCGHSA enrichment
  10. 2026-10-02 18:19 UTCVendor advisory
  11. 2026-10-02 18:19 UTCGHSA enrichment
  12. 2026-10-02 18:19 UTCEG score recompute
  13. 2026-10-02 18:19 UTCVendor advisory
  14. 2026-10-02 18:19 UTCGHSA enrichment
  15. 2026-10-02 14:38 UTCVendor advisory
  16. 2026-10-02 14:38 UTCGHSA enrichment
  17. 2026-10-02 10:52 UTCVendor advisory
  18. 2026-10-02 10:52 UTCGHSA enrichment
  19. 2026-10-02 06:53 UTCVendor advisory
  20. 2026-10-02 06:53 UTCGHSA enrichment
  21. 2026-10-02 03:12 UTCVendor advisory
  22. 2026-10-02 03:12 UTCGHSA enrichment
  23. 2026-10-01 22:58 UTCEG score recompute
  24. 2026-10-01 22:58 UTCVendor advisory
  25. 2026-10-01 22:58 UTCGHSA enrichment
  26. 2026-10-01 19:51 UTCEPSS rescore
  27. 2026-10-01 19:17 UTCVendor advisory
  28. 2026-10-01 19:17 UTCGHSA enrichment
  29. 2026-10-01 15:34 UTCVendor advisory
  30. 2026-10-01 15:34 UTCGHSA enrichment
  31. 2026-10-01 11:49 UTCVendor advisory
  32. 2026-10-01 11:49 UTCGHSA enrichment
  33. 2026-10-01 08:03 UTCVendor advisory
  34. 2026-10-01 08:03 UTCGHSA enrichment
  35. 2026-10-01 04:22 UTCVendor advisory
  36. 2026-10-01 04:22 UTCGHSA enrichment
  37. 2026-10-01 00:40 UTCVendor advisory
  38. 2026-10-01 00:40 UTCGHSA enrichment
  39. 2026-09-30 20:41 UTCVendor advisory
  40. 2026-09-30 20:40 UTCGHSA enrichment
  41. 2026-09-30 16:59 UTCEG score recompute
  42. 2026-09-30 16:59 UTCVendor advisory
  43. 2026-09-30 16:59 UTCGHSA enrichment
  44. 2026-09-30 15:04 UTCEPSS rescore
  45. 2026-09-30 12:09 UTCVendor advisory
  46. 2026-09-30 12:09 UTCGHSA enrichment
  47. 2026-09-30 08:28 UTCVendor advisory
  48. 2026-09-30 08:28 UTCGHSA enrichment
  49. 2026-09-30 04:46 UTCVendor advisory
  50. 2026-09-30 04:46 UTCGHSA enrichment
  51. 2026-09-30 00:58 UTCVendor advisory
  52. 2026-09-30 00:57 UTCGHSA enrichment
  53. 2026-09-29 18:46 UTCEG score recompute
  54. 2026-09-29 18:46 UTCVendor advisory
  55. 2026-09-29 18:45 UTCGHSA enrichment
  56. 2026-09-29 14:30 UTCVendor advisory
  57. 2026-09-29 14:30 UTCGHSA enrichment
  58. 2026-09-29 10:46 UTCVendor advisory
  59. 2026-09-29 10:46 UTCGHSA enrichment
  60. 2026-09-29 06:46 UTCVendor advisory
  61. 2026-09-29 06:46 UTCGHSA enrichment
  62. 2026-09-29 03:05 UTCVendor advisory
  63. 2026-09-29 03:05 UTCGHSA enrichment
  64. 2026-09-28 23:22 UTCEG score recompute
  65. 2026-09-28 23:22 UTCVendor advisory
  66. 2026-09-28 23:22 UTCGHSA enrichment
  67. 2026-09-28 19:41 UTCVendor advisory
  68. 2026-09-28 19:41 UTCGHSA enrichment
  69. 2026-09-28 15:38 UTCEG score recompute
  70. 2026-09-28 15:38 UTCVendor advisory
  71. 2026-09-28 15:38 UTCGHSA enrichment
  72. 2026-09-28 13:52 UTCEPSS rescore
  73. 2026-09-28 13:52 UTCEPSS rescore
  74. 2026-09-28 11:46 UTCVendor advisory
  75. 2026-09-28 11:46 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-89779?
CVE-2026-89779 is a critical vulnerability published on September 16, 2026. In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: validate ef->size covers the record's name and value When an EA record has a non-zero ef->size, ntfsreadea() only checks that the record fits in the remaining buffer (ea_size > bytes), not that ef->size is large enough to…
When was CVE-2026-89779 disclosed?
CVE-2026-89779 was first published on September 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-89779 actively exploited?
CVE-2026-89779 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (52nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-89779?
CVE-2026-89779 has a CVSS base score of 9.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-89779?
No fix for CVE-2026-89779 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-89779 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-89779

Explore →

Is Your Infrastructure Affected by CVE-2026-89779?

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

Book a Demo →Browse All CVEs