CVE-2026-90102

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

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

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

NFSv4/pnfs: key the data server cache on the NFS version

nfs4_pnfs_ds_add() keys the per-net data server cache on the multipath address set alone, and struct nfs4_pnfs_ds records no version. That suffices for the files layout driver, which always connects with version 4, but flexfiles takes its version tuple from GETDEVICEINFO per device, and one address can legitimately serve both NFSv3 and NFSv4.

Two deviceids on one address with different ds_versions[0].version therefore share a single nfs4_pnfs_ds, and whichever mirror connects first pins ds_clp to its own version. The other one is handed that client anyway, so it selects rpc_call_ops for a version the connection does not speak, and the mismatched sequence-slot handling dereferences NULL.

Add the version to the cache key so the two cannot alias, giving each version its own nfs4_pnfs_ds and connection while both mirrors stay usable. Only the major version is compared, since that is what selects rpc_call_ops and rpc_ops; v4.0 and v4.1 keep sharing a client. The files layout driver passes the 4 it already hardcodes at connect time.

CVSS v3
7.5
EG Score
7.5HIGHhigh confidence
EG Risk
39
EG Risk 39/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
Severity75% × 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 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 17, 2026

Last Modified

September 18, 2026

Advisory Details (8)

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

NFSv4/pnfs: key the data server cache on the NFS version - kernel/git/stable/linux.git - Linux kernel stable tree

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

NFSv4/pnfs: key the data server cache on the NFS version - kernel/git/stable/linux.git - Linux kernel stable tree

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

NFSv4/pnfs: key the data server cache on the NFS version - kernel/git/stable/linux.git - Linux kernel stable tree

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

NFSv4/pnfs: key the data server cache on the NFS version - kernel/git/stable/linux.git - Linux kernel stable tree

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

NFSv4/pnfs: key the data server cache on the NFS version - kernel/git/stable/linux.git - Linux kernel stable tree

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

NFSv4/pnfs: key the data server cache on the NFS version - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/27f640cd92eebf5c2f64336be7ca24f4636390cb
generic

NFSv4/pnfs: key the data server cache on the NFS version - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/13c23c5cb977f66390795437fd3837887ce1fd75
generic

NFSv4/pnfs: key the data server cache on the NFS version - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/02e160922bc83cd25e346a028ed43cbdb0b57e1a

Vendor Advisories for CVE-2026-90102(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 41× in last 7d / 104× 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 104 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-90102?
CVE-2026-90102 is a high vulnerability published on September 17, 2026. In the Linux kernel, the following vulnerability has been resolved: NFSv4/pnfs: key the data server cache on the NFS version nfs4pnfsds_add() keys the per-net data server cache on the multipath address set alone, and struct nfs4pnfsds records no version. That suffices for the files layout driver,…
When was CVE-2026-90102 disclosed?
CVE-2026-90102 was first published on September 17, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-90102 actively exploited?
CVE-2026-90102 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-90102?
CVE-2026-90102 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-90102?
No fix for CVE-2026-90102 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-90102 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-90102

Explore →

Is Your Infrastructure Affected by CVE-2026-90102?

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

Book a Demo →Browse All CVEs