CVE-2022-50241

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-09-15. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
7.8EG
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.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

NFSD: fix use-after-free on source server when doing inter-server copy

Use-after-free occurred when the laundromat tried to free expired cpntf_state entry on the s2s_cp_stateids list after inter-server copy completed. The sc_cp_list that the expired copy state was inserted on was already freed.

When COPY completes, the Linux client normally sends LOCKU(lock_state x), FREE_STATEID(lock_state x) and CLOSE(open_state y) to the source server. The nfs4_put_stid call from nfsd4_free_stateid cleans up the copy state from the s2s_cp_stateids list before freeing the lock state's stid.

However, sometimes the CLOSE was sent before the FREE_STATEID request. When this happens, the nfsd4_close_open_stateid call from nfsd4_close frees all lock states on its st_locks list without cleaning up the copy state on the sc_cp_list list. When the time the FREE_STATEID arrives the server returns BAD_STATEID since the lock state was freed. This causes the use-after-free error to occur when the laundromat tries to free the expired cpntf_state.

This patch adds a call to nfs4_free_cpntf_statelist in nfsd4_close_open_stateid to clean up the copy state before calling free_ol_stateid_reaplist to free the lock state's stid on the reaplist.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
27%
KEV
Not listed

Published

September 15, 2025

Last Modified

August 5, 2026

Advisory Details (5)

Auto-updated Aug 4, 2026
No patch confirmed yet.
generic

NFSD: fix use-after-free on source server when doing inter-server copy - kernel/git/stable/linux.git - Linux kernel stable tree

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

NFSD: fix use-after-free on source server when doing inter-server copy - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/83b94969751a691347606dbe6b1865efcfa5a643
generic

NFSD: fix use-after-free on source server when doing inter-server copy - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6ea71246b7a02af675d733e72d14bd0d591d5f4a
generic

NFSD: fix use-after-free on source server when doing inter-server copy - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/35aa0fb8c3033a3d78603356e96fc18c5b9cceb2
generic

NFSD: fix use-after-free on source server when doing inter-server copy - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/019805fea91599b22dfa62ffb29c022f35abeb06

Vendor Advisories for CVE-2022-50241(1)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:5.14.0-284.11.1.el9_22023-05-09redhat
linuxKernel @ 5.10.150osv

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.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2022-50241?
CVE-2022-50241 is a high vulnerability published on September 15, 2025. In the Linux kernel, the following vulnerability has been resolved: NFSD: fix use-after-free on source server when doing inter-server copy Use-after-free occurred when the laundromat tried to free expired cpntfstate entry on the s2scp_stateids list after inter-server copy completed. The sccplist…
When was CVE-2022-50241 disclosed?
CVE-2022-50241 was first published in the National Vulnerability Database on September 15, 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-2022-50241 actively exploited?
CVE-2022-50241 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 73.3% of all scored CVEs.
What is the CVSS score of CVE-2022-50241?
CVE-2022-50241 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2022-50241?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-50241, 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

Explore the affected products and dependency analysis for CVE-2022-50241

Explore →

Is Your Infrastructure Affected by CVE-2022-50241?

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