CVE-2022-49361

f2fs: fix to do sanity check for inline inode

MEDIUM

5.5

CVSS Score

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

Updated: August 15, 2026 at 01:36 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 for inline inode Yanming reported a kernel bug in Bugzilla kernel [1], which can be reproduced. The bug message is: The kernel message is shown below: kernel BUG at fs/inode.c:611! Call Trace: evict+0x282/0x4e0 __dentry_kill+0x2b2/0x4d0 dput+0x2dd/0x720 do_renameat2+0x596/0x970 __x64_sys_rename+0x78/0x90 do_syscall_64+0x3b/0x90 [1] https://bugzilla.kernel.org/show_bug.cgi?id=215895 The bug is due to fuzzed inode has both inline_data and encrypted flags. During f2fs_evict_inode(), as the inode was deleted by rename(), it will cause inline data conversion due to conflicting flags. The page cache will be polluted and the panic will be triggered in clear_inode(). Try fixing the bug by doing more sanity checks for inline data inode in sanity_check_inode().

Affected

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

Linux Kernel · Linux

95%

3.8 ≤ v < 5.10.1214.2 ≤ v < 5.10.1214.2 ≤ v < 5.15.464.2 ≤ v < 5.17.144.2 ≤ v < 5.18.34.2 ≤ v < 5.195.11 ≤ v < 5.15.465.16 ≤ v < 5.17.145.18 ≤ v < 5.18.34.2fcc85a4d86b5018f08717160c89c0eb50afd1dca

Vendor states this is fixed in 11c1cd032df85df3c096a57a7f27d57819956e4a (fixed)

Vendor states this is fixed in 198fd9faa271dd54dca6fc8eb6873f42dfd3b4d8 (fixed)

Vendor states this is fixed in 677a82b44ebf263d4f9a0cfbd576a6ade797a07b (fixed)

Vendor states this is fixed in 7cfe2d43becaf76e562b9617d2c2d9b445f86761 (fixed)

Vendor states this is fixed in efdefbe8b7564602ab446474788225a1f2a323b5 (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)