CVE-2026-89710

UNRATEDCVSS · not yet scoredTrending — 3 sources updated this week
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

NFSv4.1: fix layout segment leak on the pnfs_layout_process() forget path

When the server returns a new layout stateid while a valid one is still held, pnfs_layout_process() calls pnfs_mark_matching_lsegs_return() on the on-stack free_me list and jumps to out_forget. Segments whose reference count drops to zero are unlinked from lo->plh_segs and moved to free_me by mark_lseg_invalid(); for an idle cached segment the layout header holds the only reference, so this happens on the first decrement.

out_forget never drains free_me -- only the success path calls pnfs_free_lseg_list().

Commit 814b84971388 ("pNFS/NFSv4: Fix a layout segment leak in pnfs_layout_process()") added the drain; commit 08bd8dbe8882 ("pNFS/NFSv4: Try to return invalid layout in pnfs_layout_process()") removed it while switching the destination to lo->plh_return_segs, which is drained elsewhere. Commit fb700ef02676 ("NFSv4.1: Simplify layout return in pnfs_layout_process()") switched the destination back to free_me without restoring the drain.

Restore the pnfs_free_lseg_list() call.

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.2%
EPSS %ILE
6th
KEV
Not listed

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 11, 2026

Last Modified

September 14, 2026

References (7)

Vendor Advisories for CVE-2026-89710(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
—

Data Freshness Timeline

(refreshed 13× in last 7d / 44× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 50 is merged into the row it repeats.

  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  2. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  3. 2026-10-12 14:48 UTCEG score recompute
  4. 2026-10-11 19:15 UTCEG score recompute
  5. 2026-10-11 16:31 UTCEG score recompute
  6. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  7. 2026-10-11 13:47 UTCEG score recompute
  8. 2026-10-11 09:45 UTCGHSA enrichmentGHSA-84pc-7mxq-h2j8
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  10. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  11. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  12. 2026-10-08 09:12 UTCGHSA enrichmentGHSA-84pc-7mxq-h2j8
  13. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  14. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  15. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  16. 2026-10-05 09:48 UTCGHSA enrichmentGHSA-84pc-7mxq-h2j8
  17. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  18. 2026-10-02 10:24 UTCGHSA enrichmentGHSA-84pc-7mxq-h2j8
  19. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  20. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  21. 2026-09-29 11:01 UTCEG score recompute
  22. 2026-09-29 11:00 UTCGHSA enrichmentGHSA-84pc-7mxq-h2j8
  23. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  24. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  25. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 10th percentile
Show 24 more
  1. 2026-09-26 11:36 UTCGHSA enrichmentGHSA-84pc-7mxq-h2j8
  2. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  3. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  4. 2026-09-23 11:52 UTCGHSA enrichmentGHSA-84pc-7mxq-h2j8
  5. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  6. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  7. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  8. 2026-09-20 12:28 UTCGHSA enrichmentGHSA-84pc-7mxq-h2j8
  9. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  10. 2026-09-17 19:32 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  11. 2026-09-17 12:58 UTCGHSA enrichmentGHSA-84pc-7mxq-h2j8
  12. 2026-09-16 14:09 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  13. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  14. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  15. 2026-09-14 13:30 UTCGHSA enrichmentGHSA-84pc-7mxq-h2j8
  16. 2026-09-14 13:28 UTCNVD update
  17. 2026-09-14 12:27 UTCEG score recompute
  18. 2026-09-14 12:27 UTCGHSA enrichmentGHSA-84pc-7mxq-h2j8
  19. 2026-09-14 12:24 UTCMITRE cvelistV5
  20. 2026-09-13 16:48 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  21. 2026-09-12 15:02 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  22. 2026-09-11 20:36 UTCNVD update
  23. 2026-09-11 19:54 UTCEG score recompute
  24. 2026-09-11 19:53 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-89710?
CVE-2026-89710 is a vulnerability whose severity is not yet rated; its CVE record was published on September 11, 2026. In the Linux kernel, the following vulnerability has been resolved: NFSv4.1: fix layout segment leak on the pnfslayoutprocess() forget path When the server returns a new layout stateid while a valid one is still held, pnfslayoutprocess() calls pnfsmarkmatchinglsegsreturn() on the on-stack freeme…
When was the CVE record for CVE-2026-89710 published?
The CVE record for CVE-2026-89710 was published on September 11, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 14, 2026; the record at its source may have been updated since.
Is CVE-2026-89710 actively exploited?
CVE-2026-89710 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-89710?
A fix for CVE-2026-89710 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-89710 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-89710

Explore →

Is Your Infrastructure Affected by CVE-2026-89710?

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

Book a Demo →Browse All CVEs