CVE-2022-49363

f2fs: fix to do sanity check on block address in f2fs_do_zero_range()

MEDIUM

5.5

CVSS Score

Published: February 26, 2025 at 02:11 AM UTC

Updated: August 15, 2026 at 01:17 PM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.3%

Description

In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to do sanity check on block address in f2fs_do_zero_range() As Yanming reported in bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=215894 I have encountered a bug in F2FS file system in kernel v5.17. I have uploaded the system call sequence as case.c, and a fuzzed image can be found in google net disk The kernel should enable CONFIG_KASAN=y and CONFIG_KASAN_INLINE=y. You can reproduce the bug by running the following commands: kernel BUG at fs/f2fs/segment.c:2291! Call Trace: f2fs_invalidate_blocks+0x193/0x2d0 f2fs_fallocate+0x2593/0x4a70 vfs_fallocate+0x2a5/0xac0 ksys_fallocate+0x35/0x70 __x64_sys_fallocate+0x8e/0xf0 do_syscall_64+0x3b/0x90 entry_SYSCALL_64_after_hwframe+0x44/0xae The root cause is, after image was fuzzed, block mapping info in inode will be inconsistent with SIT table, so in f2fs_fallocate(), it will cause panic when updating SIT with invalid blkaddr. Let's fix the issue by adding sanity check on block address before updating SIT table with it.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

3.8 ≤ v < 5.4.1984.2 ≤ v < 5.10.1214.2 ≤ v < 5.15.464.2 ≤ v < 5.17.144.2 ≤ v < 5.18.34.2 ≤ v < 5.194.2 ≤ v < 5.4.1985.11 ≤ v < 5.15.465.16 ≤ v < 5.17.145.18 ≤ v < 5.18.35.5 ≤ v < 5.10.1214.275cd4e098d178433436abce08146a21647bb4585

Vendor states this is fixed in 25f8236213a91efdf708b9d77e9e51b6fc3e141c (fixed)

Vendor states this is fixed in 470493be19a5730ed432e3ac0f29a2ee7fc6c557 (fixed)

Vendor states this is fixed in 7361c9f2bd6a8f0cbb41cdea9aff04765ff23f67 (fixed)

Vendor states this is fixed in 805b48b234a2803cb7daec7f158af12f0fbaefac (fixed)

Vendor states this is fixed in a34d7b49894b0533222188a52e2958750f830efd (fixed)

Vendor states this is fixed in f2e1c38b5ac64eb1a16a89c52fb419409d12c25b (fixed)

Vendor states this is fixed in 4.2 (unaffected)

Vendor states this is fixed in 5.10.121 (unaffected)

Vendor states this is fixed in 5.15.46 (unaffected)

Vendor states this is fixed in 5.17.14 (unaffected)

Vendor states this is fixed in 5.18.3 (unaffected)

Vendor states this is fixed in 5.19 (unaffected)