Severity by source
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Local error-path bug needing a corrupted node block (AC:H, PR:L); impact is persisting inconsistent data to disk (I:L/A:L), no confidentiality exposure (C:N).
Primary rating from Vendor (Linux).
CVSS VectorVendor: Linux
Lifecycle Timeline
6DescriptionCVE.org
In the Linux kernel, the following vulnerability has been resolved:
f2fs: fix to clear dirty flag on folio in error path
If node block is corrupted due to chksum mismatch or inconsistent footer info, it needs to drop clear flag of node folio, in order to persist inconsistent node data to storage.
AnalysisAI
A missing dirty-flag clear on f2fs node folios in the Linux kernel's error-handling path can leave inconsistent node data unpersisted to storage, degrading on-disk filesystem consistency. The flaw is reachable only with local access (PR:L per CVSS vector) and requires encountering or supplying a corrupted f2fs node block (checksum mismatch or inconsistent footer information) to trigger the vulnerable code path. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Requires local access to a system using the f2fs filesystem and encountering (or supplying) an f2fs node block that is corrupted via checksum mismatch or inconsistent footer information - that specific error condition is what triggers the un-cleared dirty folio. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The vendor-supplied CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H = 7.8) is materially over-scored for what the patch actually describes: a missing 'clear dirty flag' on an f2fs node folio in a read/validation error path. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | Full exploit scenario with step-by-step reproduction available after sign-in. |
| Remediation | Apply the vendor-supplied patch by upgrading to Linux 6.18.51, 7.2.5, or 7.3-rc1 (or a later stable release containing the fix); for older long-term-support trees, backport the stable commits ab35ae07f2b5b4e118ea47b88577fc7d0e797b17, 3923ec2b98c96dda4a8bfab81d22553dbf0dd6c2, and 5b86eab84ac8e9289b5afc52ef88ab18ba5bacab. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, inventory all Linux systems using the f2fs filesystem and identify those running kernel versions prior to 6.18.51, 7.2.5, or 7.3-rc1. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Share
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-80432
GHSA-wf2c-cvqr-xhr7