Kernel memory compromise via nilfs_root use-after-free
Published Sep 16, 2025 · Updated Sep 16, 2025
Use-after-free in nilfs2 in Linux 4.0 through 6.4.10 allows local users to read or write kernel memory or crash the system during unmount. During nilfs2 teardown, nilfs_detach_log_writer frees nilfs_root, then iput can dirty a remaining inode and nilfs_load_inode_block dereferences the released root. Reachability requires a mounted nilfs2 image with dirty inodes and a final-reference I_DIRTY_TIME path; the result is kernel memory compromise or a kernel panic.
Summary
What happened
Use-after-free in nilfs2 in Linux 4.0 through 6.4.10 allows local users to read or write kernel memory or crash the system during unmount. During nilfs2 teardown, nilfs_detach_log_writer frees nilfs_root, then iput can dirty a remaining inode and nilfs_load_inode_block dereferences the released root. Reachability requires a mounted nilfs2 image with dirty inodes and a final-reference I_DIRTY_TIME path; the result is kernel memory compromise or a kernel panic.
The record
- CVE
- CVE-2023-53311
- Published
- Sep 16, 2025
- Updated
- Sep 16, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 16, 2025CVE publishedPublication date reported by the CVE source.
- Sep 16, 2025Record 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=0ae45f63d4ef8d8eeec49c7d8b44a1775fff13e8 <11afd67f1b3c28eb216e50a3ca8dbcb69bb71793
- Affected versionversion=0ae45f63d4ef8d8eeec49c7d8b44a1775fff13e8 <3645510cf926e6af2f4d44899370d7e5331c93bd
- Affected versionversion=0ae45f63d4ef8d8eeec49c7d8b44a1775fff13e8 <37207240872456fbab44a110bde6640445233963
- Affected versionversion=0ae45f63d4ef8d8eeec49c7d8b44a1775fff13e8 <5828d5f5dc877dcfdd7b23102e978e2ecfd86d82
- Affected versionversion=0ae45f63d4ef8d8eeec49c7d8b44a1775fff13e8 <7532ff6edbf5242376b24a95a2fefb59bb653e5a
- Affected versionversion=0ae45f63d4ef8d8eeec49c7d8b44a1775fff13e8 <a3c3b4cbf9b8554120fb230e6516e980c6277487
- Affected versionversion=0ae45f63d4ef8d8eeec49c7d8b44a1775fff13e8 <d2c539c216cce74837a9cf5804eb205939b82227
- Affected versionversion=0ae45f63d4ef8d8eeec49c7d8b44a1775fff13e8 <f8654743a0e6909dc634cbfad6db6816f10f3399
- Affected versionversion=4.0
What conditions does exploitation require?
What is affected?
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.
Public exploit references
- syzbot C reproducer for nilfs_load_inode_block use-after-freeproof of concept · demonstrated
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