Kernel memory corruption via stale log-writer timer
Published Jun 19, 2024 · Updated Aug 5, 2026
Use-after-free in the nilfs2 log writer in affected Linux kernels allows local users to corrupt kernel memory during unmount. The sc_timer callback can call wake_up_process on a freed log-writer task because the timer remains armed beyond the thread's lifetime. Access to a mounted nilfs2 volume and its teardown is required; successful triggering can panic the host or corrupt scheduler state.
Summary
What happened
Use-after-free in the nilfs2 log writer in affected Linux kernels allows local users to corrupt kernel memory during unmount. The sc_timer callback can call wake_up_process on a freed log-writer task because the timer remains armed beyond the thread's lifetime. Access to a mounted nilfs2 volume and its teardown is required; successful triggering can panic the host or corrupt scheduler state.
The record
- CVE
- CVE-2024-38583
- Published
- Jun 19, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 19, 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=2.6.35
- Affected versionversion=fdce895ea5dd4e24edf1f4d693827349a4e5b3b4 <2f12b2c03c5dae1a0de0a9e5853177e3d6eee3c6
- Affected versionversion=fdce895ea5dd4e24edf1f4d693827349a4e5b3b4 <67fa90d4a2ccd9ebb0e1e168c7d0b5d0cf3c7148
- Affected versionversion=fdce895ea5dd4e24edf1f4d693827349a4e5b3b4 <68e738be5c518fc3c4e9146b66f67c8fee0135fb
- Affected versionversion=fdce895ea5dd4e24edf1f4d693827349a4e5b3b4 <822ae5a8eac30478578a75f7e064f0584931bf2d
- Affected versionversion=fdce895ea5dd4e24edf1f4d693827349a4e5b3b4 <82933c84f188dcfe89eb26b0b48ab5d1ca99d164
- Affected versionversion=fdce895ea5dd4e24edf1f4d693827349a4e5b3b4 <86a30d6302deddb9fb97ba6fc4b04d0e870b582a
- Affected versionversion=fdce895ea5dd4e24edf1f4d693827349a4e5b3b4 <e65ccf3a4de4f0c763d94789615b83e11f204438
- Affected versionversion=fdce895ea5dd4e24edf1f4d693827349a4e5b3b4 <f5d4e04634c9cf68bdf23de08ada0bb92e8befe7
- Affected versionversion=fdce895ea5dd4e24edf1f4d693827349a4e5b3b4 <f9186bba4ea282b07293c1c892441df3a5441cb0
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