In the Linux kernel, the following vulnerability has been resolved:
nilfs2: prevent use of deleted inode
syzbot reported a WARNING in nilfs_rmdir. [1]
Because the inode bitmap is corrupted, an inode with an inode number that
should exist as a ".nilfs" file was reassigned by nilfs_mkdir for "file0",
causing an inode duplication during execution. And this causes an
underflow of i_nlink in rmdir operations.
The inode is used twice by the same task to unmount and remove directories
".nilfs" and "file0", it trigger warning in nilfs_rmdir.
Avoid to this issue, check i_nlink in nilfs_iget(), if it is 0, it means
that this inode has been deleted, and iput is executed to reclaim it.
[1]
WARNING: CPU: 1 PID: 5824 at fs/inode.c:407 drop_nlink+0xc4/0x110 fs/inode.c:407
...
Call Trace:
<TASK>
nilfs_rmdir+0x1b0/0x250 fs/nilfs2/namei.c:342
vfs_rmdir+0x3a3/0x510 fs/namei.c:4394
do_rmdir+0x3b5/0x580 fs/namei.c:4453
__do_sys_rmdir fs/namei.c:4472 [inline]
__se_sys_rmdir fs/namei.c:4470 [inline]
__x64_sys_rmdir+0x47/0x50 fs/namei.c:4470
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
nilfs2: prevent use of deleted inode
syzbot reported a WARNING in nilfs_rmdir. [1]
Because the inode bitmap is corrupted, an inode with an inode number that
should exist as a ".nilfs" file was reassigned by nilfs_mkdir for "file0",
causing an inode duplication during execution. And this causes an
underflow of i_nlink in rmdir operations.
The inode is used twice by the same task to unmount and remove directories
".nilfs" and "file0", it trigger warning in nilfs_rmdir.
Avoid to this issue, check i_nlink in nilfs_iget(), if it is 0, it means
that this inode has been deleted, and iput is executed to reclaim it.
[1]
WARNING: CPU: 1 PID: 5824 at fs/inode.c:407 drop_nlink+0xc4/0x110 fs/inode.c:407
...
Call Trace:
<TASK>
nilfs_rmdir+0x1b0/0x250 fs/nilfs2/namei.c:342
vfs_rmdir+0x3a3/0x510 fs/namei.c:4394
do_rmdir+0x3b5/0x580 fs/namei.c:4453
__do_sys_rmdir fs/namei.c:4472 [inline]
__se_sys_rmdir fs/namei.c:4470 [inline]
__x64_sys_rmdir+0x47/0x50 fs/namei.c:4470
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
Metrics
Affected Vendors & Products
Advisories
Source | ID | Title |
---|---|---|
![]() |
DLA-4075-1 | linux security update |
![]() |
DLA-4076-1 | linux-6.1 security update |
![]() |
EUVD-2024-52033 | In the Linux kernel, the following vulnerability has been resolved: nilfs2: prevent use of deleted inode syzbot reported a WARNING in nilfs_rmdir. [1] Because the inode bitmap is corrupted, an inode with an inode number that should exist as a ".nilfs" file was reassigned by nilfs_mkdir for "file0", causing an inode duplication during execution. And this causes an underflow of i_nlink in rmdir operations. The inode is used twice by the same task to unmount and remove directories ".nilfs" and "file0", it trigger warning in nilfs_rmdir. Avoid to this issue, check i_nlink in nilfs_iget(), if it is 0, it means that this inode has been deleted, and iput is executed to reclaim it. [1] WARNING: CPU: 1 PID: 5824 at fs/inode.c:407 drop_nlink+0xc4/0x110 fs/inode.c:407 ... Call Trace: <TASK> nilfs_rmdir+0x1b0/0x250 fs/nilfs2/namei.c:342 vfs_rmdir+0x3a3/0x510 fs/namei.c:4394 do_rmdir+0x3b5/0x580 fs/namei.c:4453 __do_sys_rmdir fs/namei.c:4472 [inline] __se_sys_rmdir fs/namei.c:4470 [inline] __x64_sys_rmdir+0x47/0x50 fs/namei.c:4470 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f |
![]() |
USN-7379-1 | Linux kernel vulnerabilities |
![]() |
USN-7379-2 | Linux kernel (Raspberry Pi) vulnerabilities |
![]() |
USN-7380-1 | Linux kernel (Low Latency) vulnerabilities |
![]() |
USN-7381-1 | Linux kernel (Low Latency) vulnerabilities |
![]() |
USN-7382-1 | Linux kernel (OEM) vulnerabilities |
![]() |
USN-7387-1 | Linux kernel vulnerabilities |
![]() |
USN-7387-2 | Linux kernel (FIPS) vulnerabilities |
![]() |
USN-7387-3 | Linux kernel (Real-time) vulnerabilities |
![]() |
USN-7388-1 | Linux kernel vulnerabilities |
![]() |
USN-7389-1 | Linux kernel (NVIDIA Tegra) vulnerabilities |
![]() |
USN-7390-1 | Linux kernel (Xilinx ZynqMP) vulnerabilities |
![]() |
USN-7391-1 | Linux kernel vulnerabilities |
![]() |
USN-7392-1 | Linux kernel vulnerabilities |
![]() |
USN-7392-2 | Linux kernel vulnerabilities |
![]() |
USN-7392-3 | Linux kernel (AWS) vulnerabilities |
![]() |
USN-7392-4 | Linux kernel (AWS FIPS) vulnerabilities |
![]() |
USN-7393-1 | Linux kernel (FIPS) vulnerabilities |
![]() |
USN-7401-1 | Linux kernel (AWS) vulnerabilities |
![]() |
USN-7407-1 | Linux kernel (HWE) vulnerabilities |
![]() |
USN-7413-1 | Linux kernel (IoT) vulnerabilities |
![]() |
USN-7421-1 | Linux kernel (Azure) vulnerabilities |
![]() |
USN-7458-1 | Linux kernel (IBM) vulnerabilities |
![]() |
USN-7459-1 | Linux kernel (Intel IoTG) vulnerabilities |
![]() |
USN-7459-2 | Linux kernel (GCP) vulnerabilities |
![]() |
USN-7463-1 | Linux kernel (IBM) vulnerabilities |
![]() |
USN-7513-1 | Linux kernel vulnerabilities |
![]() |
USN-7513-2 | Linux kernel (Real-time) vulnerabilities |
![]() |
USN-7513-3 | Linux kernel vulnerabilities |
![]() |
USN-7513-4 | Linux kernel (HWE) vulnerabilities |
![]() |
USN-7513-5 | Linux kernel (Oracle) vulnerabilities |
![]() |
USN-7514-1 | Linux kernel (NVIDIA) vulnerabilities |
![]() |
USN-7515-1 | Linux kernel (GKE) vulnerabilities |
![]() |
USN-7515-2 | Linux kernel vulnerabilities |
![]() |
USN-7522-1 | Linux kernel (Azure, N-Series) vulnerabilities |
![]() |
USN-7523-1 | Linux kernel (Raspberry Pi Real-time) vulnerabilities |
![]() |
USN-7524-1 | Linux kernel (Raspberry Pi) vulnerabilities |
![]() |
USN-7539-1 | Linux kernel (Raspberry Pi) vulnerabilities |
![]() |
USN-7540-1 | Linux kernel (Raspberry Pi) vulnerabilities |
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
Wed, 15 Oct 2025 21:00:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Weaknesses | NVD-CWE-noinfo | |
CPEs | cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* cpe:2.3:o:linux:linux_kernel:6.13:rc1:*:*:*:*:*:* cpe:2.3:o:linux:linux_kernel:6.13:rc2:*:*:*:*:*:* cpe:2.3:o:linux:linux_kernel:6.13:rc3:*:*:*:*:*:* |
Tue, 14 Jan 2025 08:45:00 +0000
Type | Values Removed | Values Added |
---|---|---|
References |
| |
Metrics |
threat_severity
|
cvssV3_1
|
Sat, 11 Jan 2025 12:45:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Description | In the Linux kernel, the following vulnerability has been resolved: nilfs2: prevent use of deleted inode syzbot reported a WARNING in nilfs_rmdir. [1] Because the inode bitmap is corrupted, an inode with an inode number that should exist as a ".nilfs" file was reassigned by nilfs_mkdir for "file0", causing an inode duplication during execution. And this causes an underflow of i_nlink in rmdir operations. The inode is used twice by the same task to unmount and remove directories ".nilfs" and "file0", it trigger warning in nilfs_rmdir. Avoid to this issue, check i_nlink in nilfs_iget(), if it is 0, it means that this inode has been deleted, and iput is executed to reclaim it. [1] WARNING: CPU: 1 PID: 5824 at fs/inode.c:407 drop_nlink+0xc4/0x110 fs/inode.c:407 ... Call Trace: <TASK> nilfs_rmdir+0x1b0/0x250 fs/nilfs2/namei.c:342 vfs_rmdir+0x3a3/0x510 fs/namei.c:4394 do_rmdir+0x3b5/0x580 fs/namei.c:4453 __do_sys_rmdir fs/namei.c:4472 [inline] __se_sys_rmdir fs/namei.c:4470 [inline] __x64_sys_rmdir+0x47/0x50 fs/namei.c:4470 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f | |
Title | nilfs2: prevent use of deleted inode | |
References |
|
|

Status: PUBLISHED
Assigner: Linux
Published:
Updated: 2025-05-04T09:56:57.663Z
Reserved: 2025-01-11T12:34:02.678Z
Link: CVE-2024-53690

No data.

Status : Analyzed
Published: 2025-01-11T13:15:26.470
Modified: 2025-10-15T20:47:12.663
Link: CVE-2024-53690


Updated: 2025-07-13T11:22:11Z