Local filesystem hang via writeback deadlock
Published Apr 3, 2024 · Updated May 11, 2026
Improper locking in Linux kernel nilfs2 allows local users to hang filesystem activity by racing memory migration with writeback. nilfs_page_mkwrite conditionally skips waiting for writeback on devices that do not require stable writes, letting a folio become dirty while the log writer tries to lock it. Reachability requires a NILFS2 mapping on such a device; the resulting deadlock blocks writeback, and an unclean shutdown can prevent checksum-based recovery.
Summary
What happened
Improper locking in Linux kernel nilfs2 allows local users to hang filesystem activity by racing memory migration with writeback. nilfs_page_mkwrite conditionally skips waiting for writeback on devices that do not require stable writes, letting a folio become dirty while the log writer tries to lock it. Reachability requires a NILFS2 mapping on such a device; the resulting deadlock blocks writeback, and an unclean shutdown can prevent checksum-based recovery.
The record
- CVE
- CVE-2024-26696
- Published
- Apr 3, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-667, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 3, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 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=1d1d1a767206fbe5d4c69493b7e6d2a8d08cc0a0 <228742b2ddfb99dfd71e5a307e6088ab6836272e
- Affected versionversion=1d1d1a767206fbe5d4c69493b7e6d2a8d08cc0a0 <38296afe3c6ee07319e01bb249aa4bb47c07b534
- Affected versionversion=1d1d1a767206fbe5d4c69493b7e6d2a8d08cc0a0 <7e9b622bd0748cc104d66535b76d9b3535f9dc0f
- Affected versionversion=1d1d1a767206fbe5d4c69493b7e6d2a8d08cc0a0 <8494ba2c9ea00a54d5b50e69b22c55a8958bce32
- Affected versionversion=1d1d1a767206fbe5d4c69493b7e6d2a8d08cc0a0 <862ee4422c38be5c249844a684b00d0dbe9d1e46
- Affected versionversion=1d1d1a767206fbe5d4c69493b7e6d2a8d08cc0a0 <98a4026b22ff440c7f47056481bcbbe442f607d6
- Affected versionversion=1d1d1a767206fbe5d4c69493b7e6d2a8d08cc0a0 <e38585401d464578d30f5868ff4ca54475c34f7d
- Affected versionversion=1d1d1a767206fbe5d4c69493b7e6d2a8d08cc0a0 <ea5ddbc11613b55e5128c85f57b08f907abd9b28
- Affected versionversion=3.9
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.
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