LiveActive security incident?Get immediate response
CVE Record

CVE-2024-27035: f2fs: compress: fix to guarantee persisting compressed blocks by CP

In the Linux kernel, the following vulnerability has been resolved: f2fs: compress: fix to guarantee persisting compressed blocks by CP If data block in compressed cluster is not persisted with metadata during checkpoint, after SPOR, the data may be corrupted, let's guarantee to write compressed page by checkpoint.

HighCVSS 7.3Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux F2FS checkpointing flaw can leave compressed data blocks unpersisted with their metadata. If a system then loses power unexpectedly, recovery may produce corrupted data. The issue requires local access and a relevant F2FS compressed-storage configuration; it is not described as remotely exploitable.

Executive priority

Prioritize systems using compressed F2FS where data integrity or uptime is important, especially power-loss-prone devices. This is high severity but not evidenced as actively exploited. Expedite supported kernel updates and confirm backup recoverability; lower priority where F2FS compression is absent.

Technical view

During an F2FS checkpoint, compressed data pages may not be written alongside metadata. Sudden power-off recovery can therefore encounter inconsistent persisted state, causing corruption. CVSS 3.1 is 7.3: local access, low complexity, low privileges, no user interaction, with high integrity and availability impact.

Likely exposure

Exposure is most likely on Linux systems using F2FS compression and vulnerable kernel code, particularly devices subject to abrupt power loss. The supplied affected-version data names versions from 5.6 through 6.9, but its flattened entries do not establish reliable range boundaries; confirm against distribution guidance.

Exploitation context

The bundle marks this CVE as absent from KEV and provides no evidence of active exploitation or a public exploit. Triggering depends on local access and a sudden power-off recovery condition. The practical concern is data corruption and service disruption, whether induced or accidental.

Researcher notes

The vulnerability concerns checkpoint durability rather than ordinary confidentiality exposure. The supplied CVSS indicates limited confidentiality impact but high integrity and availability impact. Multiple stable-kernel commits are cited, suggesting branch-specific backports. Exact vulnerable and fixed ranges cannot be reconstructed confidently from the flattened version list alone.

Mitigation direction

  • Install a vendor-supported kernel containing the applicable cited stable fix.
  • Check distribution advisories for exact fixed versions and backport status.
  • Maintain tested backups for systems storing important data on compressed F2FS.
  • Reduce avoidable abrupt shutdowns until affected systems are updated.

Validation and detection

  • Inventory kernel versions and compare them with distribution-specific CVE guidance.
  • Identify mounted F2FS filesystems and determine whether compression is used.
  • Verify the installed kernel includes the applicable cited fix or vendor backport.
  • Review filesystem and storage logs for corruption following unclean shutdowns.
Prepared
Confidence
high
Sources
7

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-27035 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

1CVSS vectors
3Timeline events
2ADP providers
6Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

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.

ScoreVersionSeverityVectorExploitImpactSource
7.3CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H1.85.5Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.3High
CVSS 3.1 vector shape for CVE-2024-27035Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux4c8ff7095bef64fc47e996a938f7d57f9e077da3, 4c8ff7095bef64fc47e996a938f7d57f9e077da3, 4c8ff7095bef64fc47e996a938f7d57f9e077da3, 4c8ff7095bef64fc47e996a938f7d57f9e077da3, 4c8ff7095bef64fc47e996a938f7d57f9e077da3unaffected
LinuxLinux5.6, 0, 6.1.83, 6.6.23, 6.7.11, 6.8.2, 6.9affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.