LiveActive security incident?Get immediate response
CVE Record

CVE-2023-54187: f2fs: fix potential corruption when moving a directory

In the Linux kernel, the following vulnerability has been resolved: f2fs: fix potential corruption when moving a directory F2FS has the same issue in ext4_rename causing crash revealed by xfstests/generic/707. See also commit 0813299c586b ("ext4: Fix possible corruption when moving a directory")

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 filesystem bug that can cause crash or corruption when moving a directory. The source describes it as resolved in kernel stable commits, but provides no CVSS score, CWE, or evidence of active exploitation.

Executive priority

Treat as a targeted storage-integrity issue, not a broad internet emergency. Prioritize affected Linux systems using F2FS where corruption or crash would disrupt operations.

Technical view

The issue is in F2FS directory rename handling, described as similar to an ext4_rename corruption bug and revealed by xfstests/generic/707. Exposure appears limited to affected Linux kernels using F2FS, especially where directory move operations occur.

Likely exposure

Likely exposure is Linux systems using the F2FS filesystem on affected kernel versions. Network-facing exposure is not indicated by the sources.

Exploitation context

No KEV listing or cited source indicates active exploitation. The trigger evidence cited is a filesystem regression test causing crash/corruption behavior, not a public exploit report.

Researcher notes

The bundle does not include CVSS, CWE, exploitability details, or exact fixed release mapping beyond stable commit references. Analysis should stay focused on F2FS rename behavior and kernel backport status.

Mitigation direction

  • Inventory Linux hosts using F2FS filesystems.
  • Apply kernel or distro updates containing the referenced F2FS stable fixes.
  • Check vendor guidance for exact fixed package versions.
  • Prioritize systems where F2FS stores important mutable data.
  • Ensure backups exist before kernel rollout.

Validation and detection

  • Confirm running kernels include a referenced stable commit or vendor backport.
  • Check mounted filesystems for active F2FS usage.
  • Review logs for filesystem warnings, crashes, or corruption symptoms.
  • Test directory move workloads on staging systems after patching.
Prepared
Confidence
medium
Sources
9

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-54187 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
0ADP providers
8Source links

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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux622f28ae9ba4fa89b4ff0f4a6cf75d153ea838ce, 622f28ae9ba4fa89b4ff0f4a6cf75d153ea838ce, 622f28ae9ba4fa89b4ff0f4a6cf75d153ea838ce, 622f28ae9ba4fa89b4ff0f4a6cf75d153ea838ce, 622f28ae9ba4fa89b4ff0f4a6cf75d153ea838ce, 622f28ae9ba4fa89b4ff0f4a6cf75d153ea838ce, 622f28ae9ba4fa89b4ff0f4a6cf75d153ea838ceunaffected
LinuxLinux3.19, 0, 5.4.243, 5.10.180, 5.15.112, 6.1.29, 6.2.16, 6.3.3, 6.4affected
Weakness

CWE details

No CWE listed

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