cve.bz

CVE-2024-56779 linux linux kernel

5.5 mediumEPSS 0.6%Fix available

Medium (5.5) in linux linux kernel. EPSS 0.6% estimated probability of exploitation activity in the next 30 days.

On this page
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: <TASK> dum ---truncated---

Severity

CVSS 3.1

5.5 medium
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS
0.6% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 47th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2025-10-01. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-401 Missing Release of Memory after Effective Lifetime
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2024-56779 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-56779?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-56779?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2024-56779 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2024-56779

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2024-56779](https://cve.bz/cve/badge/CVE-2024-56779.svg)](https://cve.bz/cve/CVE-2024-56779)

HTML:

<a href="https://cve.bz/cve/CVE-2024-56779"><img src="https://cve.bz/cve/badge/CVE-2024-56779.svg" alt="CVE-2024-56779"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux3.17 and later

Fixed in

ProductRelease lineFixed in
Linux5.45.4.287
Linux5.105.10.231
Linux5.155.15.174
Linux6.16.1.120
Linux6.66.6.64
Linux6.126.12.4
Linuxlater releases6.13

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian11linux5.10.234-1DLA-4075-1
Debian11linux-6.16.1.128-1~deb11u1DLA-4076-1
Debian12linux6.1.123-1DEBIAN-CVE-2024-56779
Debian13, 14linux6.12.5-1DEBIAN-CVE-2024-56779
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2024-56779
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2024-56779
Ubuntu20.04:LTSlinux5.4.0-211.231UBUNTU-CVE-2024-56779 USN-7391-1
Ubuntu20.04:LTSlinux-aws5.4.0-1142.152UBUNTU-CVE-2024-56779 USN-7392-3
Ubuntu20.04:LTSlinux-aws-5.155.15.0-1080.87~20.04.1UBUNTU-CVE-2024-56779 USN-7388-1
Ubuntu20.04:LTSlinux-azure5.4.0-1147.154UBUNTU-CVE-2024-56779 USN-7392-1
Ubuntu20.04:LTSlinux-azure-5.155.15.0-1086.95~20.04.1UBUNTU-CVE-2024-56779 USN-7421-1
Ubuntu20.04:LTSlinux-azure-fde-5.155.15.0-1086.95~20.04.1.1USN-7421-1
Ubuntu20.04:LTSlinux-bluefield5.4.0-1101.108UBUNTU-CVE-2024-56779 USN-7392-1
Ubuntu20.04:LTSlinux-gcp5.4.0-1145.154UBUNTU-CVE-2024-56779 USN-7392-1
Ubuntu20.04:LTSlinux-gcp-5.155.15.0-1081.90~20.04.1UBUNTU-CVE-2024-56779 USN-7459-2
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2024-56779
105 more for Ubuntu in the JSON and on Ubuntu's page.
Red Hatenterprise_linux:9::appstreamrv, perf, rtla and 29 more0:5.14.0-570.12.1.el9_6RHSA-2025:6966
Red Hatenterprise_linux:9::baseoskernel, kernel-64k, kernel-core and 45 more0:5.14.0-570.12.1.el9_6RHSA-2025:6966
Red Hatenterprise_linux:9::crblibperf, perf-debuginfo, kernel-debuginfo and 16 more0:5.14.0-570.12.1.el9_6RHSA-2025:6966
Red Hatenterprise_linux:9::nfvkernel-rt, kernel-rt-kvm, kernel-rt-core and 20 more0:5.14.0-570.12.1.el9_6RHSA-2025:6966
Red Hatenterprise_linux:9::realtimekernel-rt, kernel-rt-64k, kernel-rt-core and 35 more0:5.14.0-570.12.1.el9_6RHSA-2025:6966
SUSELinux Enterprise High Availability Extension 15 SP6, Linux Enterprise Live Patching 15 SP6, Linux Enterprise Module for Legacy 15 SP6 and 1 morekernel-default6.4.0-150600.23.38.1SUSE-SU-2025:0499-1
SUSELinux Enterprise Live Patching 12 SP5kernel-default4.12.14-122.261.1SUSE-SU-2025:01983-1
SUSELinux Enterprise Live Patching 12 SP5kgraft-patch-SLE12-SP5_Update_691-8.3.1SUSE-SU-2025:01983-1
SUSELinux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6-RT_Update_81-150600.1.3.1SUSE-SU-2025:0557-1
SUSELinux Enterprise Live Patching 15 SP6kernel-livepatch-SLE15-SP6_Update_81-150600.13.3.2SUSE-SU-2025:0499-1
SUSELinux Enterprise Module for Basesystem 15 SP6kernel-64kb, kernel-source, kernel-default and 1 more6.4.0-150600.23.38.1SUSE-SU-2025:0499-1
SUSELinux Enterprise Module for Basesystem 15 SP6kernel-default-base6.4.0-150600.23.38.1.150600.12.16.2SUSE-SU-2025:0499-1
SUSELinux Enterprise Module for Confidential Computing Technical Preview 15 SP6kernel-coco, kernel-syms-coco, kernel-coco_debug and 1 more6.4.0-15061.12.coco15sp6.1SUSE-SU-2025:0289-1
SUSELinux Enterprise Module for Development Tools 15 SP6kernel-docs, kernel-syms, kernel-source and 1 more6.4.0-150600.23.38.1SUSE-SU-2025:0499-1
SUSELinux Enterprise Module for Public Cloud 15 SP6kernel-azure, kernel-syms-azure, kernel-source-azure6.4.0-150600.8.26.1SUSE-SU-2025:0428-1
SUSELinux Enterprise Server 12 SP5-LTSS, Linux Enterprise Server LTSS Extended Security 12 SP5kernel-syms, kernel-source, kernel-default4.12.14-122.261.1SUSE-SU-2025:01983-1
SUSELinux Micro 6.0kernel-default-base6.4.0-24.1.21.4SUSE-SU-2025:20165-1
10 more for SUSE in the JSON and on SUSE's page.
openSUSELeap 15.6dtb-aarch64, kernel-64kb, kernel-docs and 8 more6.4.0-150600.23.38.1SUSE-SU-2025:0499-1
openSUSELeap 15.6kernel-azure, kernel-syms-azure, kernel-source-azure6.4.0-150600.8.26.1SUSE-SU-2025:0428-1
openSUSELeap 15.6kernel-default-base6.4.0-150600.23.38.1.150600.12.16.2SUSE-SU-2025:0499-1
openSUSELeap 15.6kernel-rt, kernel-syms-rt, kernel-rt_debug and 1 more6.4.0-150600.10.26.1SUSE-SU-2025:0557-1
Azure Linux2kernel5.15.176.3-1AZL-55381
Azure Linux3kernel6.6.64.2-1AZL-55349
Alpaquita23linux-lts6.1.120-r0BELL-CVE-2024-56779
Alpaquita25linux-lts6.12.41-r0BELL-CVE-2024-56779
Alpaquitastreamlinux-lts6.18.35-r1BELL-CVE-2024-56779

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · SUSE · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is rated as Moderate severity because it is limited to a denial-of-service condition through kernel memory exhaustion and does not compromise system confidentiality or integrity. On Red Hat Enterprise Linux systems, the kernel NFS server is not active by default; exposure is restricted to systems explicitly configured to export directories to NFSv4 clients. Exploitation depends on concurrent file open requests racing during client state handling, causing unreleased resource allocations within server-side state tracking.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 9kernel-0:5.14.0-570.12.1.el9_6Fixed 2025-05-13RHSA-2025:6966
Red Hat Enterprise Linux 6kernelOut of support scope
Red Hat Enterprise Linux 7kernelOut of support scope
Red Hat Enterprise Linux 7kernel-rtOut of support scope
Red Hat Enterprise Linux 8kernelOut of support scope
Red Hat Enterprise Linux 8kernel-rtOut of support scope

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2024-56779.

ICS advisories (CISA)

AdvisoryTitlePublishedSectorsAffectedFixed
ICSA-25-226-07Siemens Third-Party Components in SINEC OS2025-08-12Critical Manufacturing, Transportation Systems, Energy, Healthcare and Public Health, Financial Services, Government Services and Facilitiesnone listednone listed

From CISA's ICS advisories (CSAF), provided under CISA's notification. Only the facts are shown; each advisory is on CISA's page. Credits.

References

Check your stackJSON