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

Goal: 1000 CNY · Raised: 1020 CNY

100%

CVE-2025-38400— nfs: Clean up /proc/net/rpc/nfs when nfs_fs_proc_net_init() fails.

EPSS 0.02% · P7

Affected Version Matrix 19

VendorProductVersion RangeStatus
LinuxLinux31dd0cda5aa0547de447aaf184812f85ccc34044< 8785701fd7cd52ae74c0d2b35b82568df74e9dbbaffected
6eef21eb7a165601882dad0419a630e32d2d7a2c< 412534a1fb76958b88dca48360c6f3ad4f3390f4affected
0bbd429260821dfb81478749837d3e6377949ac6< b92397ce96743e4cc090207e2df2a856cb4cef08affected
9dd86e9d34b1078dcd647220e96a205028bf4e6f< 7701c245ff1ac1a126bf431e72b24547519046ffaffected
53a0365c9f9f66e1a981bf9188d8716d682e0739< d0877c479f44fe475f4c8c02c88ce9ad43e90298affected
d47151b79e3220e72ae323b8b8e9d6da20dc884e< 3c94212b57bedec3a386ef3da1ef00602f5c3d1daffected
d47151b79e3220e72ae323b8b8e9d6da20dc884e< 6acf340f8c1d296bcf535986175f5d0d6f2aab09affected
d47151b79e3220e72ae323b8b8e9d6da20dc884e< e8d6f3ab59468e230f3253efe5cb63efa35289f7affected
… +11 more rows
Get alerts for future matching vulnerabilitiesLog in to subscribe

I. Basic Information for CVE-2025-38400

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
nfs: Clean up /proc/net/rpc/nfs when nfs_fs_proc_net_init() fails.
Source: NVD (National Vulnerability Database)
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: nfs: Clean up /proc/net/rpc/nfs when nfs_fs_proc_net_init() fails. syzbot reported a warning below [1] following a fault injection in nfs_fs_proc_net_init(). [0] When nfs_fs_proc_net_init() fails, /proc/net/rpc/nfs is not removed. Later, rpc_proc_exit() tries to remove /proc/net/rpc, and the warning is logged as the directory is not empty. Let's handle the error of nfs_fs_proc_net_init() properly. [0]: FAULT_INJECTION: forcing a failure. name failslab, interval 1, probability 0, space 0, times 0 CPU: 1 UID: 0 PID: 6120 Comm: syz.2.27 Not tainted 6.16.0-rc1-syzkaller-00010-g2c4a1f3fe03e #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025 Call Trace: <TASK> dump_stack_lvl (lib/dump_stack.c:123) should_fail_ex (lib/fault-inject.c:73 lib/fault-inject.c:174) should_failslab (mm/failslab.c:46) kmem_cache_alloc_noprof (mm/slub.c:4178 mm/slub.c:4204) __proc_create (fs/proc/generic.c:427) proc_create_reg (fs/proc/generic.c:554) proc_create_net_data (fs/proc/proc_net.c:120) nfs_fs_proc_net_init (fs/nfs/client.c:1409) nfs_net_init (fs/nfs/inode.c:2600) ops_init (net/core/net_namespace.c:138) setup_net (net/core/net_namespace.c:443) copy_net_ns (net/core/net_namespace.c:576) create_new_namespaces (kernel/nsproxy.c:110) unshare_nsproxy_namespaces (kernel/nsproxy.c:218 (discriminator 4)) ksys_unshare (kernel/fork.c:3123) __x64_sys_unshare (kernel/fork.c:3190) do_syscall_64 (arch/x86/entry/syscall_64.c:63 arch/x86/entry/syscall_64.c:94) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:130) </TASK> [1]: remove_proc_entry: removing non-empty directory 'net/rpc', leaking at least 'nfs' WARNING: CPU: 1 PID: 6120 at fs/proc/generic.c:727 remove_proc_entry+0x45e/0x530 fs/proc/generic.c:727 Modules linked in: CPU: 1 UID: 0 PID: 6120 Comm: syz.2.27 Not tainted 6.16.0-rc1-syzkaller-00010-g2c4a1f3fe03e #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025 RIP: 0010:remove_proc_entry+0x45e/0x530 fs/proc/generic.c:727 Code: 3c 02 00 0f 85 85 00 00 00 48 8b 93 d8 00 00 00 4d 89 f0 4c 89 e9 48 c7 c6 40 ba a2 8b 48 c7 c7 60 b9 a2 8b e8 33 81 1d ff 90 <0f> 0b 90 90 e9 5f fe ff ff e8 04 69 5e ff 90 48 b8 00 00 00 00 00 RSP: 0018:ffffc90003637b08 EFLAGS: 00010282 RAX: 0000000000000000 RBX: ffff88805f534140 RCX: ffffffff817a92c8 RDX: ffff88807da99e00 RSI: ffffffff817a92d5 RDI: 0000000000000001 RBP: ffff888033431ac0 R08: 0000000000000001 R09: 0000000000000000 R10: 0000000000000001 R11: 0000000000000001 R12: ffff888033431a00 R13: ffff888033431ae4 R14: ffff888033184724 R15: dffffc0000000000 FS: 0000555580328500(0000) GS:ffff888124a62000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f71733743e0 CR3: 000000007f618000 CR4: 00000000003526f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> sunrpc_exit_net+0x46/0x90 net/sunrpc/sunrpc_syms.c:76 ops_exit_list net/core/net_namespace.c:200 [inline] ops_undo_list+0x2eb/0xab0 net/core/net_namespace.c:253 setup_net+0x2e1/0x510 net/core/net_namespace.c:457 copy_net_ns+0x2a6/0x5f0 net/core/net_namespace.c:574 create_new_namespaces+0x3ea/0xa90 kernel/nsproxy.c:110 unshare_nsproxy_namespaces+0xc0/0x1f0 kernel/nsproxy.c:218 ksys_unshare+0x45b/0xa40 kernel/fork.c:3121 __do_sys_unshare kernel/fork.c:3192 [inline] __se_sys_unshare kernel/fork.c:3190 [inline] __x64_sys_unshare+0x31/0x40 kernel/fork.c:3190 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xcd/0x490 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7fa1a6b8e929 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c ---truncated---
Source: NVD (National Vulnerability Database)
CVSS Information
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Type
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Title
Linux kernel 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞,该漏洞源于初始化失败时未清理/proc/net/rpc/nfs可能导致警告。
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

VendorProductAffected VersionsCPESubscribe
LinuxLinux 31dd0cda5aa0547de447aaf184812f85ccc34044 ~ 8785701fd7cd52ae74c0d2b35b82568df74e9dbb -
LinuxLinux 6.9 -

II. Public POCs for CVE-2025-38400

#POC DescriptionSource LinkShenlong Link
AI-Generated POCPremium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2025-38400

登录查看更多情报信息。

Same Patch Batch · Linux · 2025-07-25 · 114 CVEs total

CVE-2025-38426drm/amdgpu: Add basic validation for RAS header
CVE-2025-38440net/mlx5e: Fix race between DIM disable and net_dim()
CVE-2025-38438ASoC: SOF: Intel: hda: Use devm_kstrdup() to avoid memleak.
CVE-2025-38437ksmbd: fix potential use-after-free in oplock/lease break ack
CVE-2025-38436drm/scheduler: signal scheduled fence when kill job
CVE-2025-38435riscv: vector: Fix context save/restore with xtheadvector
CVE-2025-38434Revert "riscv: Define TASK_SIZE_MAX for __access_ok()"
CVE-2025-38433riscv: fix runtime constant support for nommu kernels
CVE-2025-38432net: netpoll: Initialize UDP checksum field before checksumming
CVE-2025-38431smb: client: fix regression with native SMB symlinks
CVE-2025-38430nfsd: nfsd4_spo_must_allow() must check this is a v4 compound request
CVE-2025-38429bus: mhi: ep: Update read pointer only after buffer is written
CVE-2025-38428Input: ims-pcu - check record size in ims_pcu_flash_firmware()
CVE-2025-38427video: screen_info: Relocate framebuffers behind PCI bridges
CVE-2025-38425i2c: tegra: check msg length in SMBUS block read
CVE-2025-38414wifi: ath12k: fix GCC_GCC_PCIE_HOT_RST definition for WCN7850
CVE-2025-38417ice: fix eswitch code memory leak in reset scenario
CVE-2025-38416NFC: nci: uart: Set tty->disc_data only in success path
CVE-2025-38415Squashfs: check return result of sb_min_blocksize
CVE-2025-38418remoteproc: core: Release rproc->clean_table after rproc_attach() fails

Showing top 20 of 114 CVEs. View all on vendor page &rarr; →

IV. Related Vulnerabilities

V. Comments for CVE-2025-38400

No comments yet


Leave a comment