Kernel warning via deleted inode reuse
Published Jan 11, 2025 · Updated May 11, 2026
Improper inode handling in Linux nilfs2 allows local users to trigger a kernel warning through operations on a corrupted NILFS2 filesystem. nilfs_iget accepts an inode whose zero i_nlink marks it as deleted, allowing nilfs_mkdir to reassign its number and duplicate the inode. Reusing that inode while removing the .nilfs and file0 directories underflows i_nlink in nilfs_rmdir; access to the mounted filesystem is required.
Summary
What happened
Improper inode handling in Linux nilfs2 allows local users to trigger a kernel warning through operations on a corrupted NILFS2 filesystem. nilfs_iget accepts an inode whose zero i_nlink marks it as deleted, allowing nilfs_mkdir to reassign its number and duplicate the inode. Reusing that inode while removing the .nilfs and file0 directories underflows i_nlink in nilfs_rmdir; access to the mounted filesystem is required.
The record
- CVE
- CVE-2024-53690
- Published
- Jan 11, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Jan 11, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.6.30
- Affected versionversion=d25006523d0b9e49fd097b2e974e7c8c05bd7f54 <284760b320a0bac411b18108316939707dccb12b
- Affected versionversion=d25006523d0b9e49fd097b2e974e7c8c05bd7f54 <55e4baa0d32f0530ddc64c26620e1f2f8fa2724c
- Affected versionversion=d25006523d0b9e49fd097b2e974e7c8c05bd7f54 <5d4ed71327b0b5f3b179a19dc3c06be9509ab3db
- Affected versionversion=d25006523d0b9e49fd097b2e974e7c8c05bd7f54 <901ce9705fbb9f330ff1f19600e5daf9770b0175
- Affected versionversion=d25006523d0b9e49fd097b2e974e7c8c05bd7f54 <912188316a8c9e41b8c1603c2276a05043b14f96
- Affected versionversion=d25006523d0b9e49fd097b2e974e7c8c05bd7f54 <ef942d233643777f7b2a5deef620e82942983143
- Affected versionversion=d25006523d0b9e49fd097b2e974e7c8c05bd7f54 <ff561987ff12b6a3233431ff659b5d332e22f153
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo