CVE-2023-54182Linux vulnerability

7 documents6 sources
Severity
N/A
No vector
EPSS
0.0%
top 92.73%
CISA KEV
Not in KEV
Exploit
No known exploits
Timeline
PublishedDec 30

Description

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

Affected Packages4 packages

Linuxlinux/linux_kernel5.2.05.15.113+2
Debianlinux/linux_kernel< 6.1.37-1+2
CVEListV5linux/linuxf824deb54b683165b953371a0529446c723ef6d6e2759a59a4cc96af712084e9db7065c858c4fe9f+4
debiandebian/linux< linux 6.1.37-1 (bookworm)

🔴Vulnerability Details

3
OSV
f2fs: fix to check readonly condition correctly2025-12-30
GHSA
GHSA-p246-5fr5-qxpv: In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to check readonly condition correctly With below case, it can mount mu2025-12-30
OSV
CVE-2023-54182: In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to check readonly condition correctly With below case, it can mount mult2025-12-30

📋Vendor Advisories

2
Red Hat
kernel: f2fs: fix to check readonly condition correctly2025-12-30
Debian
CVE-2023-54182: linux - In the Linux kernel, the following vulnerability has been resolved: f2fs: fix t...2023

🕵️Threat Intelligence

1
Wiz
CVE-2023-54182 Impact, Exploitability, and Mitigation Steps | Wiz