CVE-2025-40210

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2025-11-21. the CNA's CVSS baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

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

Revert "NFSD: Remove the cap on number of operations per NFSv4 COMPOUND"

I've found that pynfs COMP6 now leaves the connection or lease in a strange state, which causes CLOSE9 to hang indefinitely. I've dug into it a little, but I haven't been able to root-cause it yet. However, I bisected to commit 48aab1606fa8 ("NFSD: Remove the cap on number of operations per NFSv4 COMPOUND").

Tianshuo Han also reports a potential vulnerability when decoding an NFSv4 COMPOUND. An attacker can place an arbitrarily large op count in the COMPOUND header, which results in:

[ 51.410584] nfsd: vmalloc error: size 1209533382144, exceeds total pages, mode:0xdc0(GFP_KERNEL|__GFP_ZERO), nodemask=(null),cpuset=/,mems_allowed=0

when NFSD attempts to allocate the COMPOUND op array.

Let's restore the operation-per-COMPOUND limit, but increased to 200 for now.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

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%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
26%
KEV
Not listed

Published

November 21, 2025

Last Modified

August 5, 2026

Advisory Details (2)

Auto-updated Jul 31, 2026
No patch confirmed yet.
generic

Revert "NFSD: Remove the cap on number of operations per NFSv4 COMPOUND" - kernel/git/stable/linux.git - Linux kernel stable tree

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

Revert "NFSD: Remove the cap on number of operations per NFSv4 COMPOUND" - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3e7f011c255582d7c914133785bbba1990441713

Patch Availability(7)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-24.04-edge (6.17.0-14.14) @ questing2026-07-30ubuntu
ubuntulinux-tools-gcp-64k-6.17 (6.17.0-1007.7) @ questing2026-07-30ubuntu
ubuntulinux-tools-oracle-64k-6.17 (6.17.0-1007.7) @ questing2026-07-30ubuntu
ubuntulinux-tools-oem-6.17 (6.17.0-1011.11) @ noble2026-07-30ubuntu
ubuntulinux-tools-azure-6.17 (6.17.0-1008.8) @ questing2026-07-30ubuntu
redhatkernel-0:6.12.0-211.7.1.el10_22026-05-19redhat
linuxKernel @ 6.17.8osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.17.8-1~bpo13+1 (76 versions)6.17.8-1

Additional Vendor Advisories

(5)

Data Freshness Timeline

(refreshed 7× in last 7d / 34× 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 168 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2025-40210?
CVE-2025-40210 is a high vulnerability published on November 21, 2025. In the Linux kernel, the following vulnerability has been resolved: Revert "NFSD: Remove the cap on number of operations per NFSv4 COMPOUND" I've found that pynfs COMP6 now leaves the connection or lease in a strange state, which causes CLOSE9 to hang indefinitely. I've dug into it a little, but I…
When was CVE-2025-40210 disclosed?
CVE-2025-40210 was first published in the National Vulnerability Database on November 21, 2025, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-40210 actively exploited?
CVE-2025-40210 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 74.0% of all scored CVEs.
What is the CVSS score of CVE-2025-40210?
CVE-2025-40210 has a CVSS v4.0 base score of 7.5 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2025-40210?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-40210, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-40210

Explore →

Is Your Infrastructure Affected by CVE-2025-40210?

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