Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%

CVE-2024-56779— nfsd: fix nfs4_openowner leak when concurrent nfsd4_open occur

Quick assessment

Affected
Linux Linux
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞,该漏洞源于nfsd在处理并发nfsd4_open请求时,可能会导致nfs4_openowner内存泄漏,进而影响文件系统的性能和稳定性。

CVSS 9.8 · Critical EPSS 0.55% · P45

Possible ATT&CK Techniques 1 AI

T1496 · Resource Hijacking

Affected Version Matrix 16

VendorProduct Version RangeStatus
Linux Linux 3234975f477f746c22d076ea178a79ea104b2ca7< a85364f0d30dee01c5d5b4afa55a9629a8f36d8e affected
3234975f477f746c22d076ea178a79ea104b2ca7< 2d505a801e57428057563762f67a5a62009b2600 affected
3234975f477f746c22d076ea178a79ea104b2ca7< 0ab0a3ad24e970e894abcac58f85c332d1726749 affected
3234975f477f746c22d076ea178a79ea104b2ca7< 45abb68c941ebc9a35c6d3a7b08196712093c636 affected
3234975f477f746c22d076ea178a79ea104b2ca7< 37dfc81266d3a32294524bfadd3396614f8633ee affected
3234975f477f746c22d076ea178a79ea104b2ca7< 6f73f920b7ad0084373e46121d7ac34117aed652 affected
3234975f477f746c22d076ea178a79ea104b2ca7< 98100e88dd8865999dc6379a3356cd799795fe7b affected
3.17 affected
… +8 more rows
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2024-56779

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
nfsd: fix nfs4_openowner leak when concurrent nfsd4_open occur
Source: CVE Program / CVE List V5
Vulnerability Description
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---
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Source: CVE Program / CVE List V5
Vulnerability Type
N/A
Source: CVE Program / CVE List V5
Vulnerability Title
Linux kernel 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞,该漏洞源于nfsd在处理并发nfsd4_open请求时,可能会导致nfs4_openowner内存泄漏,进而影响文件系统的性能和稳定性。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

Vendor Product Affected Versions CPE Subscribe
Linux Linux 3234975f477f746c22d076ea178a79ea104b2ca7 ~ a85364f0d30dee01c5d5b4afa55a9629a8f36d8e -
Linux Linux 3.17 -

II. Public POCs for CVE-2024-56779

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2024-56779

请登录查看更多情报信息。

Patches & Fixes for CVE-2024-56779 (7)

Same Patch Batch · Linux · 2025-01-08 · 16 CVEs total

CVE-2024-56775 7.8 HIGH drm/amd/display: Fix handling of plane refcount
CVE-2024-56784 7.8 HIGH drm/amd/display: Adding array index check to prevent memory corruption
CVE-2024-56770 net/sched: netem: account for backlog updates from child qdisc
CVE-2024-56771 mtd: spinand: winbond: Fix 512GW, 01GW, 01JW and 02JW ECC information
CVE-2024-56773 kunit: Fix potential null dereference in kunit_device_driver_test()
CVE-2024-56772 kunit: string-stream: Fix a UAF bug in kunit_init_suite()
CVE-2024-56774 btrfs: add a sanity check for btrfs root in btrfs_search_slot()
CVE-2024-56776 drm/sti: avoid potential dereference of error pointers
CVE-2024-56777 drm/sti: avoid potential dereference of error pointers in sti_gdp_atomic_check
CVE-2024-56778 drm/sti: avoid potential dereference of error pointers in sti_hqvdp_atomic_check
CVE-2024-56780 quota: flush quota_release_work upon quota writeback
CVE-2024-56782 ACPI: x86: Add adev NULL check to acpi_quirk_skip_serdev_enumeration()
CVE-2024-56783 netfilter: nft_socket: remove WARN_ON_ONCE on maximum cgroup level
CVE-2024-56785 MIPS: Loongson64: DTS: Really fix PCIe port nodes for ls7a
CVE-2024-56787 soc: imx8m: Probe the SoC driver as platform driver

IV. Related Vulnerabilities

V. Comments for CVE-2024-56779

No comments yet


Leave a comment