VYPR
Unrated severityNVD Advisory· Published Dec 24, 2025· Updated Apr 15, 2026

CVE-2022-50753

CVE-2022-50753

Description

In the Linux kernel, the following vulnerability has been resolved:

f2fs: fix to do sanity check on summary info

As Wenqing Liu reported in bugzilla:

https://bugzilla.kernel.org/show_bug.cgi?id=216456

BUG: KASAN: use-after-free in recover_data+0x63ae/0x6ae0 [f2fs] Read of size 4 at addr ffff8881464dcd80 by task mount/1013

CPU: 3 PID: 1013 Comm: mount Tainted: G W 6.0.0-rc4 #1 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1 04/01/2014 Call Trace: dump_stack_lvl+0x45/0x5e print_report.cold+0xf3/0x68d kasan_report+0xa8/0x130 recover_data+0x63ae/0x6ae0 [f2fs] f2fs_recover_fsync_data+0x120d/0x1fc0 [f2fs] f2fs_fill_super+0x4665/0x61e0 [f2fs] mount_bdev+0x2cf/0x3b0 legacy_get_tree+0xed/0x1d0 vfs_get_tree+0x81/0x2b0 path_mount+0x47e/0x19d0 do_mount+0xce/0xf0 __x64_sys_mount+0x12c/0x1a0 do_syscall_64+0x38/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd

The root cause is: in fuzzed image, SSA table is corrupted: ofs_in_node is larger than ADDRS_PER_PAGE(), result in out-of-range access on 4k-size page.

  • recover_data
  • do_recover_data
  • check_index_in_prev_nodes
  • f2fs_data_blkaddr

This patch adds sanity check on summary info in recovery and GC flow in where the flows rely on them.

After patch: [ 29.310883] F2FS-fs (loop0): Inconsistent ofs_in_node:65286 in summary, ino:0, nid:6, max:1018

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

A missing sanity check in the Linux kernel's f2fs filesystem on corrupted SSA summary info can lead to a use-after-free during mount, enabling a local attacker to crash the system.

Vulnerability

Overview

CVE-2022-50753 is a use-after-free vulnerability in the Linux kernel's f2fs (Flash-Friendly File System) implementation. The root cause is the lack of a sanity check on the summary info structure read from the SSA (Segment Summary Area) table. When a specially crafted or fuzzed filesystem image is mounted, the ofs_in_node field in the summary can be larger than ADDRS_PER_PAGE(), leading to an out-of-bounds access on a 4k-sized page during recovery operations [1][2].

Exploitation

Conditions

The vulnerability is triggered during the filesystem mount process, specifically in the recover_data function and the garbage collection (GC) flow. An attacker must be able to mount a maliciously crafted f2fs image, which requires local access to the system (e.g., via a USB drive or a network filesystem). No authentication is needed beyond the ability to mount a filesystem. The attack surface is limited to systems that mount untrusted f2fs images, such as those using removable media or receiving images from untrusted sources.

Impact

A successful exploit results in a kernel crash due to a use-after-free condition, leading to a denial of service (DoS). The crash is demonstrated by a KASAN report showing a read of size 4 at a freed address during recover_data. The vulnerability does not appear to allow privilege escalation or arbitrary code execution based on the available information.

Mitigation

The fix adds a sanity check on the summary info in both the recovery and GC code paths, ensuring that ofs_in_node does not exceed the allowed maximum. The patch has been applied to the stable kernel tree [1][2]. Users should update their kernels to include the fix. No workaround is available other than avoiding the mounting of untrusted f2fs images on unpatched systems.

AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

2

Patches

6

Vulnerability mechanics

Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.

References

6

News mentions

0

No linked articles in our index yet.