CVE-2024-53690nilfs2: prevent use of deleted inode
- 5.5MediumCVSS base score
- 0.26%Exploitation in 30 daysEPSS · top 83% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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
Timeline
ID reserved
By Linux
Published
- 16 months later
· 16 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Modified | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.26% · top 83% of all CVEs (16 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected d25006523d0b9e49fd097b2e974e7c8c05bd7f54 – < 55e4baa0d32f0530ddc64c26620e1f2f8fa2724c
- affected d25006523d0b9e49fd097b2e974e7c8c05bd7f54 – < 5d4ed71327b0b5f3b179a19dc3c06be9509ab3db
- affected d25006523d0b9e49fd097b2e974e7c8c05bd7f54 – < 912188316a8c9e41b8c1603c2276a05043b14f96
- affected d25006523d0b9e49fd097b2e974e7c8c05bd7f54 – < ef942d233643777f7b2a5deef620e82942983143
- affected d25006523d0b9e49fd097b2e974e7c8c05bd7f54 – < 284760b320a0bac411b18108316939707dccb12b
- affected d25006523d0b9e49fd097b2e974e7c8c05bd7f54 – < ff561987ff12b6a3233431ff659b5d332e22f153
- affected d25006523d0b9e49fd097b2e974e7c8c05bd7f54 – < 901ce9705fbb9f330ff1f19600e5daf9770b0175
- affected 2.6.30
- unaffected < 2.6.30
- unaffected 5.4.289 – ≤ 5.4.*
- unaffected 5.10.233 – ≤ 5.10.*
- unaffected 5.15.176 – ≤ 5.15.*
- unaffected 6.1.122 – ≤ 6.1.*
- unaffected 6.6.68 – ≤ 6.6.*
- unaffected 6.12.7 – ≤ 6.12.*
- unaffected 6.13 – ≤ *
References
References9
- https://git.kernel.org/stable/c/55e4baa0d32f0530ddc64c26620e1f2f8fa2724c (opens in a new tab)
- https://git.kernel.org/stable/c/5d4ed71327b0b5f3b179a19dc3c06be9509ab3db (opens in a new tab)
- https://git.kernel.org/stable/c/912188316a8c9e41b8c1603c2276a05043b14f96 (opens in a new tab)
- https://git.kernel.org/stable/c/ef942d233643777f7b2a5deef620e82942983143 (opens in a new tab)
- https://git.kernel.org/stable/c/284760b320a0bac411b18108316939707dccb12b (opens in a new tab)
- https://git.kernel.org/stable/c/ff561987ff12b6a3233431ff659b5d332e22f153 (opens in a new tab)
- https://git.kernel.org/stable/c/901ce9705fbb9f330ff1f19600e5daf9770b0175 (opens in a new tab)
- https://lists.debian.org/debian-lts-announce/2025/03/msg00001.html (opens in a new tab)
- https://lists.debian.org/debian-lts-announce/2025/03/msg00002.html (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2024-52033 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2024-53690)Record last updated .