CVE-2022-50401

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 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

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

nfsd: under NFSv4.1, fix double svc_xprt_put on rpc_create failure

On error situation clp->cl_cb_conn.cb_xprt should not be given a reference to the xprt otherwise both client cleanup and the error handling path of the caller call to put it. Better to delay handing over the reference to a later branch.

[ 72.530665] refcount_t: underflow; use-after-free. [ 72.531933] WARNING: CPU: 0 PID: 173 at lib/refcount.c:28 refcount_warn_saturate+0xcf/0x120 [ 72.533075] Modules linked in: nfsd(OE) nfsv4(OE) nfsv3(OE) nfs(OE) lockd(OE) compat_nfs_ssc(OE) nfs_acl(OE) rpcsec_gss_krb5(OE) auth_rpcgss(OE) rpcrdma(OE) dns_resolver fscache netfs grace rdma_cm iw_cm ib_cm sunrpc(OE) mlx5_ib mlx5_core mlxfw pci_hyperv_intf ib_uverbs ib_core xt_MASQUERADE nf_conntrack_netlink nft_counter xt_addrtype nft_compat br_netfilter bridge stp llc nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip_set overlay nf_tables nfnetlink crct10dif_pclmul crc32_pclmul ghash_clmulni_intel xfs serio_raw virtio_net virtio_blk net_failover failover fuse [last unloaded: sunrpc] [ 72.540389] CPU: 0 PID: 173 Comm: kworker/u16:5 Tainted: G OE 5.15.82-dan #1 [ 72.541511] Hardware name: Red Hat KVM/RHEL-AV, BIOS 1.16.0-3.module+el8.7.0+1084+97b81f61 04/01/2014 [ 72.542717] Workqueue: nfsd4_callbacks nfsd4_run_cb_work [nfsd] [ 72.543575] RIP: 0010:refcount_warn_saturate+0xcf/0x120 [ 72.544299] Code: 55 00 0f 0b 5d e9 01 50 98 00 80 3d 75 9e 39 08 00 0f 85 74 ff ff ff 48 c7 c7 e8 d1 60 8e c6 05 61 9e 39 08 01 e8 f6 51 55 00 <0f> 0b 5d e9 d9 4f 98 00 80 3d 4b 9e 39 08 00 0f 85 4c ff ff ff 48 [ 72.546666] RSP: 0018:ffffb3f841157cf0 EFLAGS: 00010286 [ 72.547393] RAX: 0000000000000026 RBX: ffff89ac6231d478 RCX: 0000000000000000 [ 72.548324] RDX: ffff89adb7c2c2c0 RSI: ffff89adb7c205c0 RDI: ffff89adb7c205c0 [ 72.549271] RBP: ffffb3f841157cf0 R08: 0000000000000000 R09: c0000000ffefffff [ 72.550209] R10: 0000000000000001 R11: ffffb3f841157ad0 R12: ffff89ac6231d180 [ 72.551142] R13: ffff89ac6231d478 R14: ffff89ac40c06180 R15: ffff89ac6231d4b0 [ 72.552089] FS: 0000000000000000(0000) GS:ffff89adb7c00000(0000) knlGS:0000000000000000 [ 72.553175] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 72.553934] CR2: 0000563a310506a8 CR3: 0000000109a66000 CR4: 0000000000350ef0 [ 72.554874] Call Trace: [ 72.555278] [ 72.555614] svc_xprt_put+0xaf/0xe0 [sunrpc] [ 72.556276] nfsd4_process_cb_update.isra.11+0xb7/0x410 [nfsd] [ 72.557087] ? update_load_avg+0x82/0x610 [ 72.557652] ? cpuacct_charge+0x60/0x70 [ 72.558212] ? dequeue_entity+0xdb/0x3e0 [ 72.558765] ? queued_spin_unlock+0x9/0x20 [ 72.559358] nfsd4_run_cb_work+0xfc/0x270 [nfsd] [ 72.560031] process_one_work+0x1df/0x390 [ 72.560600] worker_thread+0x37/0x3b0 [ 72.561644] ? process_one_work+0x390/0x390 [ 72.562247] kthread+0x12f/0x150 [ 72.562710] ? set_kthread_struct+0x50/0x50 [ 72.563309] ret_from_fork+0x22/0x30 [ 72.563818] [ 72.564189] ---[ end trace 031117b1c72ec616 ]--- [ 72.566019] list_add corruption. next->prev should be prev (ffff89ac4977e538), but was ffff89ac4763e018. (next=ffff89ac4763e018). [ 72.567647] ------------[ cut here ]------------

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

Published

September 18, 2025

Last Modified

January 14, 2026

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 4.9.337osv

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

Frequently asked(5)

What is CVE-2022-50401?
CVE-2022-50401 is a high vulnerability published on September 18, 2025. In the Linux kernel, the following vulnerability has been resolved: nfsd: under NFSv4.1, fix double svcxprtput on rpc_create failure On error situation clp->clcbconn.cb_xprt should not be given a reference to the xprt otherwise both client cleanup and the error handling path of the caller call to…
When was CVE-2022-50401 disclosed?
CVE-2022-50401 was first published in the National Vulnerability Database on September 18, 2025, with the most recent update on January 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-50401 actively exploited?
CVE-2022-50401 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 95.1% of all scored CVEs.
What is the CVSS score of CVE-2022-50401?
CVE-2022-50401 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2022-50401?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-50401, 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-50401

Explore →

Is Your Infrastructure Affected by CVE-2022-50401?

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