{
  "cveId": "CVE-2022-49363",
  "url": "https://patchblox.com/security/cve/CVE-2022-49363",
  "summary": "CVE-2022-49363 is fixed in linux on 1 platform, first by DEBIAN-CVE-2022-49363, released February 26, 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 block address in...",
  "description": "In the Linux kernel, the following vulnerability has been resolved:  f2fs: fix to do sanity check on block address in f2fs_do_zero_range()  As Yanming reported in bugzilla:  https://bugzilla.kernel.org/show_bug.cgi?id=215894  I have encountered a bug in F2FS file system in kernel v5.17.  I have uploaded the system call sequence as case.c, and a fuzzed image can be found in google net disk  The kernel should enable CONFIG_KASAN=y and CONFIG_KASAN_INLINE=y. You can reproduce the bug by running the following commands:  kernel BUG at fs/f2fs/segment.c:2291! Call Trace:  f2fs_invalidate_blocks\u002B0x193/0x2d0  f2fs_fallocate\u002B0x2593/0x4a70  vfs_fallocate\u002B0x2a5/0xac0  ksys_fallocate\u002B0x35/0x70  __x64_sys_fallocate\u002B0x8e/0xf0  do_syscall_64\u002B0x3b/0x90  entry_SYSCALL_64_after_hwframe\u002B0x44/0xae  The root cause is, after image was fuzzed, block mapping info in inode will be inconsistent with SIT table, so in f2fs_fallocate(), it will cause panic when updating SIT with invalid blkaddr.  Let\u0027s fix the issue by adding sanity check on block address before updating SIT table with it.",
  "published": "2025-02-26T07:01:12Z",
  "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.00277,
  "epssPercentile": 0.20206,
  "priority": "Routine",
  "priorityTier": 4,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "fixes": [
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 12.15 (bookworm)",
      "fixedVersion": "5.18.5-1",
      "fix": "DEBIAN-CVE-2022-49363",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-49363",
      "released": "2025-02-26T07:01:12Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 13.5 (trixie)",
      "fixedVersion": "5.18.5-1",
      "fix": "DEBIAN-CVE-2022-49363",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-49363",
      "released": "2025-02-26T07:01:12Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 14",
      "fixedVersion": "5.18.5-1",
      "fix": "DEBIAN-CVE-2022-49363",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-49363",
      "released": "2025-02-26T07:01:12Z"
    }
  ],
  "noFixYet": [],
  "dataAsOf": "2026-11-08T19:12:23Z",
  "attribution": {
    "text": "Data: Patchblox Patch Radar",
    "url": "https://patchblox.com/security/patch-radar",
    "terms": "https://patchblox.com/security/patch-radar/use-the-data"
  }
}