CVE-2024-53690: nilfs2: prevent use of deleted inode
In the Linux kernel, the following vulnerability has been resolved:
nilfs2: prevent use of deleted inode
syzbot reported a WARNING in nilfsrmdir. [1]
Because the inode bitmap is corrupted, an inode with an inode number that should exist as a ".nilfs" file was reassigned by nilfsmkdir for "file0", causing an inode duplication during execution. And this causes an underflow of inlink in rmdir operations.
The inode is used twice by the same task to unmount and remove directories ".nilfs" and "file0", it trigger warning in nilfsrmdir.
Avoid to this issue, check inlink in nilfsiget(), 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 dropnlink+0xc4/0x110 fs/inode.c:407 ... Call Trace: <TASK> nilfsrmdir+0x1b0/0x250 fs/nilfs2/namei.c:342 vfsrmdir+0x3a3/0x510 fs/namei.c:4394 dormdir+0x3b5/0x580 fs/namei.c:4453 dosysrmdir fs/namei.c:4472 [inline] sesysrmdir fs/namei.c:4470 [inline] x64sysrmdir+0x47/0x50 fs/namei.c:4470 dosyscallx64 arch/x86/entry/common.c:52 [inline] dosyscall64+0xf3/0x230 arch/x86/entry/common.c:83 entrySYSCALL64afterhwframe+0x77/0x7f
Other sources
This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.
— Launchpad
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-53690?
CVE-2024-53690 is considered to be of medium severity, involving the potential misuse of a deleted inode in the Linux kernel.
How do I fix CVE-2024-53690?
To address CVE-2024-53690, ensure that your Linux kernel is updated to a version that includes the patch for this vulnerability.
Which systems are affected by CVE-2024-53690?
CVE-2024-53690 affects the Linux kernel, specifically systems utilizing the nilfs2 file system.
What are the potential impacts of CVE-2024-53690?
The impact of CVE-2024-53690 could include data corruption due to the improper reassignment of inode numbers, leading to potential system instability.
Was CVE-2024-53690 publicly disclosed?
Yes, CVE-2024-53690 was publicly disclosed following a report by syzbot, highlighting a warning in the nilfs_rmdir function.