Filesystem corruption via uncleared dirty node folio
Published Sep 16, 2026 · Updated Sep 16, 2026
Improper error handling in Linux F2FS allows local users to persist corrupted node data through a malformed filesystem image. In __get_node_folio(), the error path cleared the folio's uptodate flag instead of its dirty flag after checksum or footer validation failed, permitting later writeback of invalid node contents. Reaching the path requires processing a corrupted F2FS node block, and mounting an attacker-supplied image ordinarily requires administrative access.
Summary
What happened
Improper error handling in Linux F2FS allows local users to persist corrupted node data through a malformed filesystem image. In __get_node_folio(), the error path cleared the folio's uptodate flag instead of its dirty flag after checksum or footer validation failed, permitting later writeback of invalid node contents. Reaching the path requires processing a corrupted F2FS node block, and mounting an attacker-supplied image ordinarily requires administrative access.
The record
- CVE
- CVE-2026-89832
- Published
- Sep 16, 2026
- Updated
- Sep 16, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Sep 16, 2026CVE publishedPublication date reported by the CVE source.
- Sep 16, 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=4.19.51 <4.20
- Affected versionversion=5.1.10 <5.2
- Affected versionversion=5.2
- Affected versionversion=8d7ebdd109b4654ec5e0e9c3c6f08b06d6558f10
- Affected versionversion=b039536485970829918aa237a08417bd0ed5437c
- Affected versionversion=b42b179bda9ff11075a6fc2bac4d9e400513679a <3923ec2b98c96dda4a8bfab81d22553dbf0dd6c2
- Affected versionversion=b42b179bda9ff11075a6fc2bac4d9e400513679a <5b86eab84ac8e9289b5afc52ef88ab18ba5bacab
- Affected versionversion=b42b179bda9ff11075a6fc2bac4d9e400513679a <ab35ae07f2b5b4e118ea47b88577fc7d0e797b17
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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
No sourced classifications are available.
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