CVE-2023-53796 json
f2fs: fix information leak in f2fs_move_inline_dirents()
published 2025-12-09 11 mo ago modified 2026-06-17 4 mo ago also EUVD-2023-60110
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 11%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
f2fs: fix information leak in f2fs_move_inline_dirents()
When converting an inline directory to a regular one, f2fs is leaking uninitialized memory to disk because it doesn't initialize the entire directory block. Fix this by zero-initializing the block.
This bug was introduced by commit 4ec17d688d74 ("f2fs: avoid unneeded initializing when converting inline dentry"), which didn't consider the security implications of leaking uninitialized memory to disk.
This was found by running xfstest generic/435 on a KMSAN-enabled kernel.
Patch / fix
- Linux Linux 4.14.308, 4.19.276, 5.4.235, 5.10.173, 5.15.99, 6.1.16, 6.2.3, 6.3
- linux Debian 14, Debian 13, Debian 12 6.1.20-1
debian advisories DEBIAN-CVE-2023-53796
- linux Ubuntu 20.04 LTS 5.4.0-152.169
- linux Ubuntu 22.04 LTS 5.15.0-75.82
- linux-aws Ubuntu 20.04 LTS 5.4.0-1104.112
- linux-aws Ubuntu 22.04 LTS 5.15.0-1038.43
- linux-gcp Ubuntu 20.04 LTS 5.4.0-1107.116
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1036.44
- linux-gke Ubuntu 22.04 LTS 5.15.0-1036.41
- linux-ibm Ubuntu 20.04 LTS 5.4.0-1051.56
ubuntu advisories UBUNTU-CVE-2023-53796
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/4e3b4b170bd43db1d8a93a6bd0ea434b17cc86f7 commit
- git.kernel.org/stable/c/a6807ef0f3b3d8508d3b07a2e35de8a91820a014 commit
- git.kernel.org/stable/c/2bef8314fcf94ddc27e22d03f237c0fafd00de33 commit
- git.kernel.org/stable/c/00b5587326625d0fddb2a5f5a3d4acd950102ace commit
- git.kernel.org/stable/c/117d4f6687b1f74423b5d398ea95c63b262a8e73 commit
- git.kernel.org/stable/c/f07a8d61b6ea81bb3cbe0638af40f8824d6147fd commit
- git.kernel.org/stable/c/eebaecef0095bb8f493c03982da75c6e7bae1056 commit
- git.kernel.org/stable/c/9a5571cff4ffcfc24847df9fd545cc5799ac0ee5 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2023-53796 updated
kernel: f2fs: fix information leak in f2fs_move_inline_dirents()
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.21% chance of exploitation in the next 30 days, higher than 11% of all scored CVEs (FIRST EPSS, 2026-11-08).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/4e3b4b170bd43db1d8a93a6bd0ea434b17cc86f7
- git.kernel.org /stable/c/a6807ef0f3b3d8508d3b07a2e35de8a91820a014
- git.kernel.org /stable/c/2bef8314fcf94ddc27e22d03f237c0fafd00de33
- git.kernel.org /stable/c/00b5587326625d0fddb2a5f5a3d4acd950102ace
- git.kernel.org /stable/c/117d4f6687b1f74423b5d398ea95c63b262a8e73
- git.kernel.org /stable/c/f07a8d61b6ea81bb3cbe0638af40f8824d6147fd
- git.kernel.org /stable/c/eebaecef0095bb8f493c03982da75c6e7bae1056
- git.kernel.org /stable/c/9a5571cff4ffcfc24847df9fd545cc5799ac0ee5
Sources
- CVE List CVE-2023-53796
- NVD CVE-2023-53796
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.