CVE-2026-89836

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.8EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: 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: fix folio_nr_pages() race after put in large folio invalidate

Our v6.18 based Android system is continuely suffering livelock and bad page stat as shown in[1] which related to broken xarray slot status. By investigating big folio operations within f2fs, we find below races and fix it by get the nr_pages before drop the refcount and folio_lock.

f2fs_get_read_data_folio() calls f2fs_folio_put() before folio_nr_pages() when invalidating a large folio from the page cache. That unlocks the folio and drops the caller reference, leaving a window where a concurrent truncate or folio split can shrink the compound folio or free it before the invalidate range is computed. An undersized range then leaves split sub-folios in mapping->i_pages, which can later interact badly with truncate and reclaim (stale xarray entries and bad page state when folio->mapping no longer matches the mapping being truncated).

[1] PID: 2594 TASK: ffffff8169b81580 CPU: 7 COMMAND: "Thread-3" #0 [ffffffc08ef2b8a0] xas_load at ffffffe52d1f42a4 #1 [ffffffc08ef2b900] find_get_entries at ffffffe52c185798 #2 [ffffffc08ef2bb60] truncate_inode_pages_range at ffffffe52c19e83c #3 [ffffffc08ef2bbc0] truncate_inode_pages_final at ffffffe52c19ec2c #4 [ffffffc08ef2bc20] f2fs_evict_inode at ffffffe52c4c8400 #5 [ffffffc08ef2bcc0] evict at ffffffe52c2de9f4 #6 [ffffffc08ef2bd00] iput at ffffffe52c2db1b4 #7 [ffffffc08ef2bd30] dentry_unlink_inode at ffffffe52c2d7204 #8 [ffffffc08ef2bd50] __dentry_kill at ffffffe52c2d3dcc #9 [ffffffc08ef2bd80] dput at ffffffe52c2d3c3c #10 [ffffffc08ef2bda0] __fput at ffffffe52c2b0a7c #11 [ffffffc08ef2bde0] ____fput at ffffffe52c2b1034 #12 [ffffffc08ef2bdf0] task_work_run at ffffffe52beea200 #13 [ffffffc08ef2be20] exit_to_user_mode_loop at ffffffe52bfbc17c #14 [ffffffc08ef2be80] el0_svc at ffffffe52d1f8e54 #15 [ffffffc08ef2beb0] el0t_64_sync_handler at ffffffe52d1f8d10

CVSS v3
7.8
EG Score
7.8HIGHhigh confidence
EG Risk
40
EG Risk 40/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
Severity78% × 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.2%
EPSS %ILE
5th
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 16, 2026

Last Modified

September 16, 2026

Advisory Details (2)

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

f2fs: fix folio_nr_pages() race after put in large folio invalidate - kernel/git/stable/linux.git - Linux kernel stable tree

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

f2fs: fix folio_nr_pages() race after put in large folio invalidate - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0dab71381f1b4d12dc2056f8bd5aaa9d93ce9082

Vendor Advisories for CVE-2026-89836(1)

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

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (178 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-89836?
CVE-2026-89836 is a high vulnerability published on September 16, 2026. In the Linux kernel, the following vulnerability has been resolved: f2fs: fix folionrpages() race after put in large folio invalidate Our v6.18 based Android system is continuely suffering livelock and bad page stat as shown in[1] which related to broken xarray slot status. By investigating big…
When was CVE-2026-89836 disclosed?
CVE-2026-89836 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-89836 actively exploited?
CVE-2026-89836 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-89836?
CVE-2026-89836 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-89836?
No fix for CVE-2026-89836 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-89836 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-89836

Explore →

Is Your Infrastructure Affected by CVE-2026-89836?

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

Book a Demo →Browse All CVEs