{
  "cveId": "CVE-2022-49170",
  "url": "https://patchblox.com/security/cve/CVE-2022-49170",
  "summary": "CVE-2022-49170 is fixed in linux on 1 platform, first by DEBIAN-CVE-2022-49170, released February 26, 2025. It is not reported as exploited. Patch Radar priority: High.",
  "title": "linux: In the Linux kernel, the following vulnerability has been resolved:  f2fs: fix to do sanity check on curseg-\u003Ealloc_ty...",
  "description": "In the Linux kernel, the following vulnerability has been resolved:  f2fs: fix to do sanity check on curseg-\u003Ealloc_type  As Wenqing Liu reported in bugzilla:  https://bugzilla.kernel.org/show_bug.cgi?id=215657  - Overview UBSAN: array-index-out-of-bounds in fs/f2fs/segment.c:3460:2 when mount and operate a corrupted image  - Reproduce tested on kernel 5.17-rc4, 5.17-rc6  1. mkdir test_crash 2. cd test_crash 3. unzip tmp2.zip 4. mkdir mnt 5. ./single_test.sh f2fs 2  - Kernel dump [   46.434454] loop0: detected capacity change from 0 to 131072 [   46.529839] F2FS-fs (loop0): Mounted with checkpoint version = 7548c2d9 [   46.738319] ================================================================================ [   46.738412] UBSAN: array-index-out-of-bounds in fs/f2fs/segment.c:3460:2 [   46.738475] index 231 is out of range for type \u0027unsigned int [2]\u0027 [   46.738539] CPU: 2 PID: 939 Comm: umount Not tainted 5.17.0-rc6 #1 [   46.738547] Hardware name: QEMU Standard PC (Q35 \u002B ICH9, 2009), BIOS 1.13.0-1ubuntu1.1 04/01/2014 [   46.738551] Call Trace: [   46.738556]  \u003CTASK\u003E [   46.738563]  dump_stack_lvl\u002B0x47/0x5c [   46.738581]  ubsan_epilogue\u002B0x5/0x50 [   46.738592]  __ubsan_handle_out_of_bounds\u002B0x68/0x80 [   46.738604]  f2fs_allocate_data_block\u002B0xdff/0xe60 [f2fs] [   46.738819]  do_write_page\u002B0xef/0x210 [f2fs] [   46.738934]  f2fs_do_write_node_page\u002B0x3f/0x80 [f2fs] [   46.739038]  __write_node_page\u002B0x2b7/0x920 [f2fs] [   46.739162]  f2fs_sync_node_pages\u002B0x943/0xb00 [f2fs] [   46.739293]  f2fs_write_checkpoint\u002B0x7bb/0x1030 [f2fs] [   46.739405]  kill_f2fs_super\u002B0x125/0x150 [f2fs] [   46.739507]  deactivate_locked_super\u002B0x60/0xc0 [   46.739517]  deactivate_super\u002B0x70/0xb0 [   46.739524]  cleanup_mnt\u002B0x11a/0x200 [   46.739532]  __cleanup_mnt\u002B0x16/0x20 [   46.739538]  task_work_run\u002B0x67/0xa0 [   46.739547]  exit_to_user_mode_prepare\u002B0x18c/0x1a0 [   46.739559]  syscall_exit_to_user_mode\u002B0x26/0x40 [   46.739568]  do_syscall_64\u002B0x46/0xb0 [   46.739584]  entry_SYSCALL_64_after_hwframe\u002B0x44/0xae  The root cause is we missed to do sanity check on curseg-\u003Ealloc_type, result in out-of-bound accessing on sbi-\u003Eblock_count[] array, fix it.",
  "published": "2025-02-26T07:00:54Z",
  "severity": "high",
  "cvss": 7.8,
  "cvssVector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
  "epss": 0.00283,
  "epssPercentile": 0.20936,
  "priority": "High",
  "priorityTier": 3,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "fixes": [
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 12.15 (bookworm)",
      "fixedVersion": "5.17.3-1",
      "fix": "DEBIAN-CVE-2022-49170",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-49170",
      "released": "2025-02-26T07:00:54Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 13.5 (trixie)",
      "fixedVersion": "5.17.3-1",
      "fix": "DEBIAN-CVE-2022-49170",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-49170",
      "released": "2025-02-26T07:00:54Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 14",
      "fixedVersion": "5.17.3-1",
      "fix": "DEBIAN-CVE-2022-49170",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-49170",
      "released": "2025-02-26T07:00:54Z"
    }
  ],
  "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"
  }
}