---
id: CVE-2022-49361
title: |-
  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
summary: |-
  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…
severity: medium
cvss: 5.5
cvssVector: 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'
vendor: linux
product: linux_kernel
affected:
  - 'linux_kernel >= 3.8, < 5.10.121'
  - 'linux_kernel >= 5.11, < 5.15.46'
  - 'linux_kernel >= 5.16, < 5.17.14'
  - 'linux_kernel >= 5.18, < 5.18.3'
patched:
  - linux_kernel 5.18.3
published: '2025-02-26'
updated: '2026-08-15'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2022-49361'
references:
  - url: 'https://git.kernel.org/stable/c/11c1cd032df85df3c096a57a7f27d57819956e4a'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/198fd9faa271dd54dca6fc8eb6873f42dfd3b4d8'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/677a82b44ebf263d4f9a0cfbd576a6ade797a07b'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/7cfe2d43becaf76e562b9617d2c2d9b445f86761'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/efdefbe8b7564602ab446474788225a1f2a323b5'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
tags:
  - nvd
epss: 0.00261
epssPercentile: 0.15913
ingestedAt: '2026-08-15T13:26:43.899Z'
---

## Overview

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

- `linux_kernel >= 3.8, < 5.10.121`
- `linux_kernel >= 5.11, < 5.15.46`
- `linux_kernel >= 5.16, < 5.17.14`
- `linux_kernel >= 5.18, < 5.18.3`

## Remediation

Upgrade past the affected range:

- `linux_kernel 5.18.3`