Service interruption via post-read-only log writes
Published Sep 17, 2025 · Updated Sep 17, 2025
Improper state handling in Linux nilfs2 allows local users to interrupt service after metadata corruption forces read-only mode. nilfs_segctor_do_construct() continues log construction and passes buffer heads whose uptodate flag was cleared to mark_buffer_dirty(). Reachability requires a mounted NILFS2 filesystem already degraded by metadata corruption; the published impact is availability loss only.
Summary
What happened
Improper state handling in Linux nilfs2 allows local users to interrupt service after metadata corruption forces read-only mode. nilfs_segctor_do_construct() continues log construction and passes buffer heads whose uptodate flag was cleared to mark_buffer_dirty(). Reachability requires a mounted NILFS2 filesystem already degraded by metadata corruption; the published impact is availability loss only.
The record
- CVE
- CVE-2023-53337
- Published
- Sep 17, 2025
- Updated
- Sep 17, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 17, 2025CVE publishedPublication date reported by the CVE source.
- Sep 17, 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 <13f73ef77baa4764dc1ca4fcbae9cade05b83866
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <28a65b49eb53e172d23567005465019658bfdb4d
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <4005cec6847c06ee191583270b7cdd7e696543cc
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <4569a292a84e340e97d178898ad1cfe1a3080a61
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <55f7810632f993cff622a0ddbc7c865892294b61
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7c3e662048053802f6b0db3a78e97f4e1f7edc4f
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a73201c607d8e506358d60aafddda4246bdd9350
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <bd89073fc7a5d03b1d06b372addbe405e5a925f4
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <e9c5412c5972124776c1b873533eb39e287a4dfa
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.
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