LiveActive security incident?Get immediate response
CVE Record

CVE-2023-52682: f2fs: fix to wait on block writeback for post_read case

In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to wait on block writeback for post_read case If inode is compressed, but not encrypted, it missed to call f2fs_wait_on_block_writeback() to wait for GCed page writeback in IPU write path. Thread A GC-Thread - f2fs_gc - do_garbage_collect - gc_data_segment - move_data_block - f2fs_submit_page_write migrate normal cluster's block via meta_inode's page cache - f2fs_write_single_data_page - f2fs_do_write_data_page - f2fs_inplace_write_data - f2fs_submit_page_bio IRQ - f2fs_read_end_io IRQ old data overrides new data due to out-of-order GC and common IO. - f2fs_read_end_io

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel F2FS data-integrity flaw. Under a specific compressed-but-not-encrypted file condition, garbage collection and normal writes could complete out of order, allowing old data to overwrite newer data. The source does not provide CVSS, active exploitation evidence, or broad impact detail.

Executive priority

Treat this as a targeted kernel maintenance issue unless F2FS compression is important in your environment. There is no cited active exploitation, but the potential outcome is data corruption, so affected storage workloads should be patched through normal urgent maintenance.

Technical view

The issue is in F2FS IPU write handling for compressed, non-encrypted inodes. The vulnerable path missed f2fs_wait_on_block_writeback() for post_read handling, creating an ordering race between GC block migration and normal I/O that can result in stale data replacing new data.

Likely exposure

Exposure is most likely on Linux systems using F2FS with file compression enabled and encryption absent on affected kernel builds. Systems not using F2FS, or not using this compressed non-encrypted condition, are less likely exposed based on the provided description.

Exploitation context

The bundle says KEV is false and provides no public exploitation claim. The described scenario is a race in kernel filesystem I/O involving garbage collection and writeback ordering, suggesting reliability and data-integrity risk rather than a confirmed remote attack path.

Researcher notes

Evidence is limited to the CVE description and kernel stable references. The impact is grounded in the described stale-data overwrite race. No CVSS, CWE, exploit status, or distribution-specific fixed package versions are included in the supplied bundle.

Mitigation direction

  • Apply vendor kernel updates containing the referenced F2FS stable fixes.
  • Check Linux distribution advisories for backported fixes in packaged kernels.
  • Prioritize systems using F2FS compression for remediation review.
  • Avoid changing production filesystem settings without vendor guidance and testing.

Validation and detection

  • Inventory Linux hosts and identify any F2FS-mounted filesystems.
  • Confirm whether F2FS compression is used on affected systems.
  • Check kernel package changelogs for the referenced stable commit fixes.
  • Verify updated kernels are booted, not merely installed.
  • Review storage integrity alerts or unexplained file corruption reports.
Prepared
Confidence
medium
Sources
7

Public sources used

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-2023-52682 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

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

SSVC decision data

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

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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux4c8ff7095bef64fc47e996a938f7d57f9e077da3, 4c8ff7095bef64fc47e996a938f7d57f9e077da3, 4c8ff7095bef64fc47e996a938f7d57f9e077da3, 4c8ff7095bef64fc47e996a938f7d57f9e077da3, 4c8ff7095bef64fc47e996a938f7d57f9e077da3unaffected
LinuxLinux5.6, 0, 5.15.209, 6.1.75, 6.6.14, 6.7.2, 6.8affected
Weakness

CWE details

No CWE listed

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