{
  "cveId": "CVE-2022-50273",
  "url": "https://patchblox.com/security/cve/CVE-2022-50273",
  "summary": "CVE-2022-50273 is fixed in linux on 1 platform, first by DEBIAN-CVE-2022-50273, released September 15, 2025. It is not reported as exploited. Patch Radar priority: Routine.",
  "title": "linux: In the Linux kernel, the following vulnerability has been resolved:  f2fs: fix to do sanity check on destination blka...",
  "description": "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\u002B0xa55/0x10b0 [f2fs] Call Trace:  \u003CTASK\u003E  f2fs_do_replace_block\u002B0xa98/0x1890 [f2fs]  f2fs_replace_block\u002B0xeb/0x180 [f2fs]  recover_data\u002B0x1a69/0x6ae0 [f2fs]  f2fs_recover_fsync_data\u002B0x120d/0x1fc0 [f2fs]  f2fs_fill_super\u002B0x4665/0x61e0 [f2fs]  mount_bdev\u002B0x2cf/0x3b0  legacy_get_tree\u002B0xed/0x1d0  vfs_get_tree\u002B0x81/0x2b0  path_mount\u002B0x47e/0x19d0  do_mount\u002B0xce/0xf0  __x64_sys_mount\u002B0x12c/0x1a0  do_syscall_64\u002B0x38/0x90  entry_SYSCALL_64_after_hwframe\u002B0x63/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\u0027s validation in SIT table, and skip f2fs_replace_block() to avoid inconsistent status.",
  "published": "2025-09-15T15:15:38Z",
  "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",
  "epss": 0.00159,
  "epssPercentile": 0.05123,
  "priority": "Routine",
  "priorityTier": 4,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "fixes": [
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 12.15 (bookworm)",
      "fixedVersion": "6.0.3-1",
      "fix": "DEBIAN-CVE-2022-50273",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-50273",
      "released": "2025-09-15T15:15:38Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 13.5 (trixie)",
      "fixedVersion": "6.0.3-1",
      "fix": "DEBIAN-CVE-2022-50273",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-50273",
      "released": "2025-09-15T15:15:38Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 14",
      "fixedVersion": "6.0.3-1",
      "fix": "DEBIAN-CVE-2022-50273",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-50273",
      "released": "2025-09-15T15:15:38Z"
    }
  ],
  "noFixYet": [],
  "dataAsOf": "2026-11-08T13:06:02Z",
  "attribution": {
    "text": "Data: Patchblox Patch Radar",
    "url": "https://patchblox.com/security/patch-radar",
    "terms": "https://patchblox.com/security/patch-radar/use-the-data"
  }
}