CVE-2024-27034: f2fs: compress: fix to cover normal cluster write with cp_rwsem
In the Linux kernel, the following vulnerability has been resolved:
f2fs: compress: fix to cover normal cluster write with cp_rwsem
When we overwrite compressed cluster w/ normal cluster, we should
not unlock cp_rwsem during f2fs_write_raw_pages(), otherwise data
will be corrupted if partial blocks were persisted before CP & SPOR,
due to cluster metadata wasn't updated atomically.
Security readout for executives and security teams
Plain-English summary
A Linux F2FS filesystem flaw can corrupt data when a compressed storage cluster is overwritten as a normal cluster and a checkpoint or sudden power loss interrupts the operation. Exploitation requires local access and specific filesystem activity; it is not described as a remote attack.
Executive priority
Treat as a high-priority integrity and availability issue for systems actively using compressed F2FS, especially shared or locally untrusted hosts. Other Linux systems can be triaged lower after confirming F2FS is absent. Schedule vendor-supported updates and ensure recoverable backups rather than treating this as an internet-wide emergency.
Technical view
F2FS released cp_rwsem while f2fs_write_raw_pages() handled a compressed-to-normal cluster overwrite. If only some blocks persisted before a checkpoint and sudden-power-off recovery, cluster metadata and data could become inconsistent because they were not updated atomically. The supplied CVSS v3.1 score is 7.8 with local, low-privilege access and no user interaction.
Likely exposure
Exposure is most likely on Linux systems using F2FS compression where local users or processes can trigger relevant writes. Systems not using F2FS, or not exercising compressed-cluster overwrites, are unlikely to encounter this specific flaw. The supplied version data is ambiguous, so confirm exposure through the kernel or distribution vendor.
Exploitation context
The supplied record does not identify active exploitation, and the CVE is not listed as KEV in the bundle. The CVSS vector indicates a local attack requiring low privileges, low complexity, and no user interaction. Evidence supports a conditional data-corruption risk, not a remotely exploitable compromise.
Researcher notes
The vulnerable behavior concerns atomicity across normal writes, checkpointing, and sudden-power-off recovery during compressed-cluster conversion. The source bundle provides six stable-kernel commits but does not clearly map each correction to its release line. It also provides no public exploit evidence, CWE classification, or reliable per-distribution package mapping.
Mitigation direction
Apply a vendor-supported kernel update containing the applicable stable F2FS correction.
Prioritize systems using F2FS compression or supporting untrusted local workloads.
Check Linux distribution advisories for precise affected and corrected package versions.
Maintain verified backups and recovery procedures for exposed F2FS data.
Validation and detection
Identify systems mounting F2FS filesystems and determine whether compression is enabled.
Record running kernel and package versions, then compare them with vendor advisories.
Confirm the installed kernel includes the applicable referenced stable fix.
After updating, verify the corrected kernel is running and filesystems mount normally.
Review filesystem and kernel logs for corruption or recovery warnings.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-27034 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.