Kernel crash via uncleared rollforward inode list
Published Sep 18, 2024 · Updated Aug 5, 2026
Use-after-free in Linux nilfs2 before 6.11 allows local users to trigger invalid inode access during mount-time rollforward recovery. The failure path releases the recovery root without first removing recovered inodes from ns_dirty_files, leaving stale entries that later reference freed objects. Reachability requires local low-privilege access and a nilfs2 volume with partial dsync logs plus a recovery error; the documented consequence is kernel service interruption.
Summary
What happened
Use-after-free in Linux nilfs2 before 6.11 allows local users to trigger invalid inode access during mount-time rollforward recovery. The failure path releases the recovery root without first removing recovered inodes from ns_dirty_files, leaving stale entries that later reference freed objects. Reachability requires local low-privilege access and a nilfs2 volume with partial dsync logs plus a recovery error; the documented consequence is kernel service interruption.
The record
- CVE
- CVE-2024-46781
- Published
- Sep 18, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 18, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 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=0f3e1c7f23f8a6f8224fa1d275381f6d9279ad4b <07e4dc2fe000ab008bcfe90be4324ef56b5b4355
- Affected versionversion=0f3e1c7f23f8a6f8224fa1d275381f6d9279ad4b <1cf1f7e8cd47244fa947d357ef1f642d91e219a3
- Affected versionversion=0f3e1c7f23f8a6f8224fa1d275381f6d9279ad4b <35a9a7a7d94662146396199b0cfd95f9517cdd14
- Affected versionversion=0f3e1c7f23f8a6f8224fa1d275381f6d9279ad4b <5787fcaab9eb5930f5378d6a1dd03d916d146622
- Affected versionversion=0f3e1c7f23f8a6f8224fa1d275381f6d9279ad4b <8e2d1e9d93c4ec51354229361ac3373058529ec4
- Affected versionversion=0f3e1c7f23f8a6f8224fa1d275381f6d9279ad4b <9d8c3a585d564d776ee60d4aabec59b404be7403
- Affected versionversion=0f3e1c7f23f8a6f8224fa1d275381f6d9279ad4b <ca92c4bff2833cb30d493b935168d6cccd5c805d
- Affected versionversion=0f3e1c7f23f8a6f8224fa1d275381f6d9279ad4b <da02f9eb333333b2e4f25d2a14967cff785ac82e
- Affected versionversion=2.6.30
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