Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ CVE-2023-54182 — kernel

🟠 CVSS 7.1 — High ✅ No Known Exploit NVD
7.1
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

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

How this vulnerability can be exploited

This issue can be reached with local access to the system, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity high, availability high.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

  • Attack vector: Local — a local account, shell or session on the host is needed.
  • Attack complexity: Low — the attack works reliably, with no preparation.
  • Privileges required: Low — an ordinary user account is enough.
  • User interaction: None — nobody has to be tricked into anything.
  • Scope: Unchanged — the damage stays inside the vulnerable component.
  • Confidentiality impact: None.
  • Integrity impact: High — total loss, or loss the attacker controls.
  • Availability impact: High — total loss, or loss the attacker controls.

Affected software

CVE-2023-54182 is recorded against 2 packages.

  • kernel (from 6.2.0 up to 6.3.4)
  • unknown

Timeline and source

Published on 30 December 2025 and last revised on 12 August 2026. No public exploit is currently recorded for this entry. Record sourced from NVD.

References

git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
git.kernel.org (Web)
github.com (Advisory)
nvd.nist.gov (Advisory)
git.kernel.org (Package)

Other advisories for this package

kernel has other advisories on record. If you are patching this one, these are worth checking on the same host:

CVE-2023-54182 on other distributions

Each distribution ships its own build and its own fixed version. Pick the one you run:

Details

Severity High
CVSS Score 7.1
CVSS Vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
CWE N/A
Public Exploit ✅ No
Source NVD
Published 2025-12-30
Updated 2026-08-20
Modified 2026-08-12
Fix URL N/A

Affected Packages

Software From version Fixed in
kernel 6.2.0 6.3.4
unknown — —

Similar Threats

Site Security Check

Is kernel part of your stack?

CVE-2023-54182 is rated CVSS 7.1 High. BotEraser scans your installation against known CVE records and tells you whether this vulnerability applies to the versions you actually run.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesCVECVE 2023
✓