Kernel memory corruption via NILFS2 teardown race
Published Oct 4, 2025 · Updated Oct 4, 2025
Use-after-free in the Linux kernel NILFS2 component allows local users to corrupt kernel memory through repeated filesystem teardown. nilfs_segctor_thread clears sc_task before notifying sc_wait_task, letting nilfs_segctor_kill_thread observe completion and free nilfs_sc_info while the first thread still uses its waitqueue. Access to mount and unmount a NILFS2 volume is required; winning the race can produce a kernel crash or support local privilege escalation.
Summary
What happened
Use-after-free in the Linux kernel NILFS2 component allows local users to corrupt kernel memory through repeated filesystem teardown. nilfs_segctor_thread clears sc_task before notifying sc_wait_task, letting nilfs_segctor_kill_thread observe completion and free nilfs_sc_info while the first thread still uses its waitqueue. Access to mount and unmount a NILFS2 volume is required; winning the race can produce a kernel crash or support local privilege escalation.
The record
- CVE
- CVE-2023-53608
- Published
- Oct 4, 2025
- Updated
- Oct 4, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 4, 2025CVE publishedPublication date reported by the CVE source.
- Oct 4, 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=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <034cce77d52ba013ce62b4f5258c29907eb1ada5
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0dbf0e64b91ee8fcb278aea93eb06fc7d56ecbcc
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <613bf23c070d11c525268f2945aa594704a9b764
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6be49d100c22ffea3287a4b19d7639d259888e33
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <92684e02654c91a61a0b0561433b710bcece19fe
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b4d80bd6370b81a1725b6b8f7894802c23a14e9f
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <bae009a2f1b7c2011d2e92d8c84868d315c0b97e
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f32297dba338dc06d62286dedb3cdbd5175b1719
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
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