CVE-2024-56779

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2025-01-08. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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

nfsd: fix nfs4_openowner leak when concurrent nfsd4_open occur

The action force umount(umount -f) will attempt to kill all rpc_task even umount operation may ultimately fail if some files remain open. Consequently, if an action attempts to open a file, it can potentially send two rpc_task to nfs server.

NFS CLIENT thread1 thread2 open("file") ... nfs4_do_open _nfs4_do_open _nfs4_open_and_get_state _nfs4_proc_open nfs4_run_open_task /* rpc_task1 */ rpc_run_task rpc_wait_for_completion_task

umount -f nfs_umount_begin rpc_killall_tasks rpc_signal_task rpc_task1 been wakeup and return -512 _nfs4_do_open // while loop ... nfs4_run_open_task /* rpc_task2 */ rpc_run_task rpc_wait_for_completion_task

While processing an open request, nfsd will first attempt to find or allocate an nfs4_openowner. If it finds an nfs4_openowner that is not marked as NFS4_OO_CONFIRMED, this nfs4_openowner will released. Since two rpc_task can attempt to open the same file simultaneously from the client to server, and because two instances of nfsd can run concurrently, this situation can lead to lots of memory leak. Additionally, when we echo 0 to /proc/fs/nfsd/threads, warning will be triggered.

NFS SERVER nfsd1 nfsd2 echo 0 > /proc/fs/nfsd/threads

nfsd4_open nfsd4_process_open1 find_or_alloc_open_stateowner // alloc oo1, stateid1 nfsd4_open nfsd4_process_open1 find_or_alloc_open_stateowner // find oo1, without NFS4_OO_CONFIRMED release_openowner unhash_openowner_locked list_del_init(&oo->oo_perclient) // cannot find this oo // from client, LEAK!!! alloc_stateowner // alloc oo2

nfsd4_process_open2 init_open_stateid // associate oo1 // with stateid1, stateid1 LEAK!!! nfs4_get_vfs_file // alloc nfsd_file1 and nfsd_file_mark1 // all LEAK!!!

nfsd4_process_open2 ...

write_threads ... nfsd_destroy_serv nfsd_shutdown_net nfs4_state_shutdown_net nfs4_state_destroy_net destroy_client __destroy_client // won't find oo1!!! nfsd_shutdown_generic nfsd_file_cache_shutdown kmem_cache_destroy for nfsd_file_slab and nfsd_file_mark_slab // bark since nfsd_file1 // and nfsd_file_mark1 // still alive

======================================================================= BUG nfsd_file (Not tainted): Objects remaining in nfsd_file on __kmem_cache_shutdown() -----------------------------------------------------------------------

Slab 0xffd4000004438a80 objects=34 used=1 fp=0xff11000110e2ad28 flags=0x17ffffc0000240(workingset|head|node=0|zone=2|lastcpupid=0x1fffff) CPU: 4 UID: 0 PID: 757 Comm: sh Not tainted 6.12.0-rc6+ #19 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.1-2.fc37 04/01/2014 Call Trace: dum ---truncated---

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
25(Track)
EG Risk 25/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
Severity55% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
44%
KEV
Not listed

Published

January 8, 2025

Last Modified

August 5, 2026

Advisory Details (7)

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

nfsd: fix nfs4_openowner leak when concurrent nfsd4_open occur - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/98100e88dd8865999dc6379a3356cd799795fe7b
generic

nfsd: fix nfs4_openowner leak when concurrent nfsd4_open occur - kernel/git/stable/linux.git - Linux kernel stable tree

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

nfsd: fix nfs4_openowner leak when concurrent nfsd4_open occur - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/37dfc81266d3a32294524bfadd3396614f8633ee
generic

nfsd: fix nfs4_openowner leak when concurrent nfsd4_open occur - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/45abb68c941ebc9a35c6d3a7b08196712093c636
generic

nfsd: fix nfs4_openowner leak when concurrent nfsd4_open occur - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0ab0a3ad24e970e894abcac58f85c332d1726749
generic

nfsd: fix nfs4_openowner leak when concurrent nfsd4_open occur - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2d505a801e57428057563762f67a5a62009b2600
generic

nfsd: fix nfs4_openowner leak when concurrent nfsd4_open occur - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a85364f0d30dee01c5d5b4afa55a9629a8f36d8e

Vendor Advisories for CVE-2024-56779(1)

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

Patch Availability(31)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-21.21) @ oracular2026-05-30ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.135.133) @ jammy2026-05-30ubuntu
ubuntulinux-tools-lowlatency-hwe-24.04-edge (6.11.0-1011.12~24.04.1) @ noble2026-05-30ubuntu
ubuntulinux-tools-lowlatency-64k (6.11.0-1011.12) @ oracular2026-05-30ubuntu
ubuntulinux-tools-oem-24.04b (6.11.0-1017.17) @ noble2026-05-30ubuntu
ubuntulinux-tools-kvm (5.15.0.1076.72) @ jammy2026-05-30ubuntu
ubuntulinux-tools-realtime (5.15.0.1080.83) @ jammy2026-05-30ubuntu
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1044.48) @ jammy2026-05-30ubuntu
ubuntulinux-tools-nvidia-tegra-rt (5.15.0.1033.33) @ jammy2026-05-30ubuntu
ubuntulinux-tools-gcp-fips (5.15.0.1079.69) @ jammy2026-05-30ubuntu
ubuntulinux-tools-iot (5.4.0.1048.46) @ focal2026-05-30ubuntu
ubuntulinux-virtual-hwe-18.04-edge (5.4.0.211.206) @ focal2026-05-30ubuntu
ubuntulinux-tools-aws-fips (5.4.0.1142.89) @ focal2026-05-30ubuntu
ubuntulinux-tools-aws-edge (5.4.0.1142.152~18.04.1) @ bionic2026-05-30ubuntu
ubuntulinux-tools-fips (5.4.0.1116.113) @ focal2026-05-30ubuntu
ubuntulinux-tools-aws-lts-20.04 (5.4.0.1142.139) @ focal2026-05-30ubuntu
ubuntulinux-tools-oracle-edge (5.4.0.1140.149~18.04.1) @ bionic2026-05-30ubuntu
ubuntulinux-tools-raspi (6.11.0-1010.10) @ oracular2026-05-30ubuntu
ubuntulinux-tools-gcp-fips (5.4.0.1145.87) @ focal2026-05-30ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.136.147~20.04.1) @ focal2026-05-30ubuntu
ubuntulinux-tools-azure-fde-edge (5.15.0.1086.95~20.04.1.61) @ focal2026-05-30ubuntu
ubuntulinux-virtual (6.8.0-58.60) @ noble2026-05-30ubuntu
ubuntulinux-tools-gcp-edge (6.8.0-1028.30~22.04.1) @ jammy2026-05-30ubuntu
ubuntulinux-tools-aws-edge (6.8.0-1027.29~22.04.1) @ jammy2026-05-30ubuntu
ubuntulinux-tools-ibm-edge (5.15.0.1074.77~20.04.1) @ focal2026-05-30ubuntu
ubuntulinux-tools-gkeop-6.8 (6.8.0-1010.12) @ noble2026-05-30ubuntu
ubuntulinux-tools-ibm-edge (5.4.0.1090.95~18.04.1) @ bionic2026-05-30ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1081.90~20.04.1) @ focal2026-05-30ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-58.60~22.04.1) @ jammy2026-05-30ubuntu
redhatkernel-0:5.14.0-570.12.1.el9_62025-05-13redhat
linuxKernel @ 5.4.287—osv

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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (44 versions)5.10.234-1—
linux-6.16.1.106-3~deb11u1, 6.1.106-3~deb11u2, 6.1.106-3~deb11u3, 6.1.112-1~deb11u1, 6.1.119-1~deb11u16.1.128-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (32 versions)6.1.123-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—6.12.5-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—6.12.5-1—

Weakness Classification(1)

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

Additional Vendor Advisories

(24)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2024-56779?
CVE-2024-56779 is a medium vulnerability published on January 8, 2025. In the Linux kernel, the following vulnerability has been resolved: nfsd: fix nfs4openowner leak when concurrent nfsd4open occur The action force umount(umount -f) will attempt to kill all rpc_task even umount operation may ultimately fail if some files remain open. Consequently, if an action…
When was CVE-2024-56779 disclosed?
CVE-2024-56779 was first published in the National Vulnerability Database on January 8, 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-2024-56779 actively exploited?
CVE-2024-56779 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 56.2% of all scored CVEs.
What is the CVSS score of CVE-2024-56779?
CVE-2024-56779 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-56779?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-56779, 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-2024-56779

Explore →

Is Your Infrastructure Affected by CVE-2024-56779?

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

Start Free Scan →Browse All CVEs