Kernel crash or hang via unsynchronized nilfs2 writeback
Published Jun 25, 2024 · Updated Aug 5, 2026
Race condition in the Linux nilfs2 filesystem allows local users to crash or hang the kernel through destructive block-device writes. The log writer starts writeback for segment-summary or super-root pages without waiting for existing backing-device page-cache writeback, leaving the writeback state inconsistent. Exploitation requires local write access to the block device underlying a mounted nilfs2 filesystem and can trigger a kernel BUG or stalled writeback.
Summary
What happened
Race condition in the Linux nilfs2 filesystem allows local users to crash or hang the kernel through destructive block-device writes. The log writer starts writeback for segment-summary or super-root pages without waiting for existing backing-device page-cache writeback, leaving the writeback state inconsistent. Exploitation requires local write access to the block device underlying a mounted nilfs2 filesystem and can trigger a kernel BUG or stalled writeback.
The record
- CVE
- CVE-2024-37078
- Published
- Jun 25, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 25, 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.30
- Affected versionversion=9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 <0ecfe3a92869a59668d27228dabbd7965e83567f
- Affected versionversion=9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 <1f3bff69f1214fe03a02bc650d5bbfaa6e65ae7d
- Affected versionversion=9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 <271dcd977ccda8c7a26e360425ae7b4db7d2ecc0
- Affected versionversion=9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 <33900d7eae616647e179eee1c66ebe654ee39627
- Affected versionversion=9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 <614d397be0cf43412b3f94a0f6460eddced8ce92
- Affected versionversion=9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 <95f6f81e50d858a7c9aa7c795ec14a0ac3819118
- Affected versionversion=9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 <a4ca369ca221bb7e06c725792ac107f0e48e82e7
- Affected versionversion=9ff05123e3bfbb1d2b68ba1d9bf1f7d1dffc1453 <a75b8f493dfc48aa38c518430bd9e03b53bffebe
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