---
id: CVE-2022-50273
title: |-
  In the Linux kernel, the following vulnerability has been resolved:

  f2fs: fix to do sanity check on destination blkaddr during recovery

  As Wenqing Liu reported in bugzilla:

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

  loop5: de…
summary: |-
  In the Linux kernel, the following vulnerability has been resolved:

  f2fs: fix to do sanity check on destination blkaddr during recovery

  As Wenqing Liu reported in bugzilla:

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

  loop5: de…
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.4.220'
  - 'linux_kernel >= 5.5, < 5.10.150'
  - 'linux_kernel >= 5.11, < 5.15.75'
  - 'linux_kernel >= 5.16, < 5.19.17'
  - 'linux_kernel >= 6.0, < 6.0.3'
patched:
  - linux_kernel 6.0.3
published: '2025-09-15'
updated: '2026-08-15'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2022-50273'
references:
  - url: 'https://git.kernel.org/stable/c/0ef4ca04a3f9223ff8bc440041c524b2123e09a3'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/3a4d24d746866dd45d970bd565ff3886e839366a'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/68b1e607559d3dc85f94b0d738d7c4e8029b0cfa'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/73fb4bd2c055a393816f078f158cdd3025006f1d'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/8f0a47def4722c5fd8d6b9268b5ffed8a249e2db'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/ed854f10e6afd5cbd5c3274d4c4df4bfe0ab4362'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
tags:
  - nvd
epss: 0.00156
epssPercentile: 0.0514
ingestedAt: '2026-08-15T13:26:45.450Z'
---

## Overview

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

f2fs: fix to do sanity check on destination blkaddr during recovery

As Wenqing Liu reported in bugzilla:

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

loop5: detected capacity change from 0 to 131072
F2FS-fs (loop5): recover_inode: ino = 6, name = hln, inline = 1
F2FS-fs (loop5): recover_data: ino = 6 (i_size: recover) err = 0
F2FS-fs (loop5): recover_inode: ino = 6, name = hln, inline = 1
F2FS-fs (loop5): recover_data: ino = 6 (i_size: recover) err = 0
F2FS-fs (loop5): recover_inode: ino = 6, name = hln, inline = 1
F2FS-fs (loop5): recover_data: ino = 6 (i_size: recover) err = 0
F2FS-fs (loop5): Bitmap was wrongly set, blk:5634
------------[ cut here ]------------
WARNING: CPU: 3 PID: 1013 at fs/f2fs/segment.c:2198
RIP: 0010:update_sit_entry+0xa55/0x10b0 [f2fs]
Call Trace:
 <TASK>
 f2fs_do_replace_block+0xa98/0x1890 [f2fs]
 f2fs_replace_block+0xeb/0x180 [f2fs]
 recover_data+0x1a69/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

If we enable CONFIG_F2FS_CHECK_FS config, it will trigger a kernel panic
instead of warning.

The root cause is: in fuzzed image, SIT table is inconsistent with inode
mapping table, result in triggering such warning during SIT table update.

This patch introduces a new flag DATA_GENERIC_ENHANCE_UPDATE, w/ this
flag, data block recovery flow can check destination blkaddr's validation
in SIT table, and skip f2fs_replace_block() to avoid inconsistent status.

## Affected

- `linux_kernel >= 3.8, < 5.4.220`
- `linux_kernel >= 5.5, < 5.10.150`
- `linux_kernel >= 5.11, < 5.15.75`
- `linux_kernel >= 5.16, < 5.19.17`
- `linux_kernel >= 6.0, < 6.0.3`

## Remediation

Upgrade past the affected range:

- `linux_kernel 6.0.3`