LiveActive security incident?Get immediate response
CVE Record

CVE-2023-54182: f2fs: fix to check readonly condition correctly

In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to check readonly condition correctly With below case, it can mount multi-device image w/ rw option, however one of secondary device is set as ro, later update will cause panic, so let's introduce f2fs_dev_is_readonly(), and check multi-devices rw status in f2fs_remount() w/ it in order to avoid such inconsistent mount status. mkfs.f2fs -c /dev/zram1 /dev/zram0 -f blockdev --setro /dev/zram1 mount -t f2fs dev/zram0 /mnt/f2fs mount: /mnt/f2fs: WARNING: source write-protected, mounted read-only. mount -t f2fs -o remount,rw mnt/f2fs dd if=/dev/zero of=/mnt/f2fs/file bs=1M count=8192 kernel BUG at fs/f2fs/inline.c:258! RIP: 0010:f2fs_write_inline_data+0x23e/0x2d0 [f2fs] Call Trace: f2fs_write_single_data_page+0x26b/0x9f0 [f2fs] f2fs_write_cache_pages+0x389/0xa60 [f2fs] __f2fs_write_data_pages+0x26b/0x2d0 [f2fs] f2fs_write_data_pages+0x2e/0x40 [f2fs] do_writepages+0xd3/0x1b0 __writeback_single_inode+0x5b/0x420 writeback_sb_inodes+0x236/0x5a0 __writeback_inodes_wb+0x56/0xf0 wb_writeback+0x2a3/0x490 wb_do_writeback+0x2b2/0x330 wb_workfn+0x6a/0x260 process_one_work+0x270/0x5e0 worker_thread+0x52/0x3e0 kthread+0xf4/0x120 ret_from_fork+0x29/0x50

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Linux kernel flaw can let an incorrectly remounted F2FS multi-device filesystem trigger a kernel panic. The practical business risk is availability loss on systems that use F2FS and permit local storage or mount administration. The sources do not show active exploitation.

Executive priority

Prioritize patching where Linux systems use F2FS for production workloads or appliances. For environments without F2FS, this is lower urgency but should still be handled through normal kernel maintenance.

Technical view

F2FS failed to correctly check readonly state across all devices in a multi-device filesystem during remount. A secondary device marked read-only could still lead to a read-write remount state, and later writes could hit a kernel BUG in F2FS inline data handling.

Likely exposure

Exposure is most likely on Linux systems using F2FS multi-device filesystems. General Linux hosts not using F2FS, or without local mount/remount capability, are less likely exposed. Distribution backport status is not provided in the bundle.

Exploitation context

CISA KEV status is false. The source bundle provides a crash scenario but no evidence of exploitation in the wild. The scenario requires control over F2FS mount/remount behavior and writable activity against an inconsistent multi-device setup.

Researcher notes

The bundle identifies a logic flaw in F2FS readonly checks and references stable kernel commits. It does not provide CVSS, CWE, distro-specific fixed versions, or external exploitation reports, so exposure assessment depends on local filesystem usage and vendor kernel status.

Mitigation direction

  • Apply vendor kernel updates that include the referenced F2FS readonly check fixes.
  • Check Linux distribution advisories for backported fixes to supported kernels.
  • Avoid read-write remounts of F2FS multi-device filesystems with any read-only component.
  • Restrict local privileges that allow mounting, remounting, or block-device state changes.
  • Monitor for kernel panic reports involving F2FS writeback or inline data paths.

Validation and detection

  • Inventory systems using F2FS, especially multi-device F2FS filesystems.
  • Confirm running kernel versions against vendor advisories and the referenced stable fixes.
  • Review storage configurations for read-only secondary devices in F2FS deployments.
  • Check system logs for F2FS kernel BUG or panic traces.
  • Verify mount/remount privileges are limited to trusted administrators.
Prepared
Confidence
medium
Sources
6

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-54182 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
5Source 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.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxf824deb54b683165b953371a0529446c723ef6d6, f824deb54b683165b953371a0529446c723ef6d6, f824deb54b683165b953371a0529446c723ef6d6, f824deb54b683165b953371a0529446c723ef6d6unaffected
LinuxLinux5.2, 0, 5.15.113, 6.1.30, 6.3.4, 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.