- Vulnerability/
- CVE-2024-53690
CVE-2024-53690: nilfs2: prevent use of deleted inode
First published: Sat Jan 11 2025(Updated: )
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
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Linux Kernel | ||
| debian/linux | <=5.10.223-1 | 5.10.234-1 6.1.129-1 6.1.133-1 6.12.22-1 |
| debian/linux-6.1 | 6.1.129-1~deb11u1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://git.kernel.org/stable/c/284760b320a0bac411b18108316939707dccb12b
- https://git.kernel.org/stable/c/55e4baa0d32f0530ddc64c26620e1f2f8fa2724c
- https://git.kernel.org/stable/c/5d4ed71327b0b5f3b179a19dc3c06be9509ab3db
- https://git.kernel.org/stable/c/901ce9705fbb9f330ff1f19600e5daf9770b0175
- https://git.kernel.org/stable/c/912188316a8c9e41b8c1603c2276a05043b14f96
- https://git.kernel.org/stable/c/ef942d233643777f7b2a5deef620e82942983143
- https://git.kernel.org/stable/c/ff561987ff12b6a3233431ff659b5d332e22f153
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-53690
- https://nvd.nist.gov/vuln/detail/CVE-2024-53690
- https://launchpad.net/bugs/cve/CVE-2024-53690
- https://security-tracker.debian.org/tracker/CVE-2024-53690
- https://ubuntu.com/security/CVE-2024-53690
- https://git.kernel.org/linus/901ce9705fbb9f330ff1f19600e5daf9770b0175
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.
- agent/severity
- agent/title
- agent/first-publish-date
- agent/type
- collector/nvd-api
- source/NVD
- agent/author
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- collector/usn-cve
- source/Ubuntu
- collector/nvd-cve
- collector/launchpad-cve
- source/Launchpad
- agent/references
- agent/description
- agent/source
- agent/softwarecombine
- agent/tags
- agent/event
- collector/security-tracker-debian
- source/Debian
- vendor/linux
- canonical/linux kernel
- package-manager/debian