{
  "cveId": "CVE-2022-49763",
  "url": "https://patchblox.com/security/cve/CVE-2022-49763",
  "summary": "CVE-2022-49763 is fixed in linux on 1 platform, first by DEBIAN-CVE-2022-49763, released May 1, 2025. It is not reported as exploited. Patch Radar priority: High.",
  "title": "linux: In the Linux kernel, the following vulnerability has been resolved:  ntfs: fix use-after-free in ntfs_attr_find()  Pa...",
  "description": "In the Linux kernel, the following vulnerability has been resolved:  ntfs: fix use-after-free in ntfs_attr_find()  Patch series \u0022ntfs: fix bugs about Attribute\u0022, v2.  This patchset fixes three bugs relative to Attribute in record:  Patch 1 adds a sanity check to ensure that, attrs_offset field in first mft record loading from disk is within bounds.  Patch 2 moves the ATTR_RECORD\u0027s bounds checking earlier, to avoid dereferencing ATTR_RECORD before checking this ATTR_RECORD is within bounds.  Patch 3 adds an overflow checking to avoid possible forever loop in ntfs_attr_find().  Without patch 1 and patch 2, the kernel triggersa KASAN use-after-free detection as reported by Syzkaller.  Although one of patch 1 or patch 2 can fix this, we still need both of them.  Because patch 1 fixes the root cause, and patch 2 not only fixes the direct cause, but also fixes the potential out-of-bounds bug.   This patch (of 3):  Syzkaller reported use-after-free read as follows: ================================================================== BUG: KASAN: use-after-free in ntfs_attr_find\u002B0xc02/0xce0 fs/ntfs/attrib.c:597 Read of size 2 at addr ffff88807e352009 by task syz-executor153/3607  [...] Call Trace:  \u003CTASK\u003E  __dump_stack lib/dump_stack.c:88 [inline]  dump_stack_lvl\u002B0xcd/0x134 lib/dump_stack.c:106  print_address_description mm/kasan/report.c:317 [inline]  print_report.cold\u002B0x2ba/0x719 mm/kasan/report.c:433  kasan_report\u002B0xb1/0x1e0 mm/kasan/report.c:495  ntfs_attr_find\u002B0xc02/0xce0 fs/ntfs/attrib.c:597  ntfs_attr_lookup\u002B0x1056/0x2070 fs/ntfs/attrib.c:1193  ntfs_read_inode_mount\u002B0x89a/0x2580 fs/ntfs/inode.c:1845  ntfs_fill_super\u002B0x1799/0x9320 fs/ntfs/super.c:2854  mount_bdev\u002B0x34d/0x410 fs/super.c:1400  legacy_get_tree\u002B0x105/0x220 fs/fs_context.c:610  vfs_get_tree\u002B0x89/0x2f0 fs/super.c:1530  do_new_mount fs/namespace.c:3040 [inline]  path_mount\u002B0x1326/0x1e20 fs/namespace.c:3370  do_mount fs/namespace.c:3383 [inline]  __do_sys_mount fs/namespace.c:3591 [inline]  __se_sys_mount fs/namespace.c:3568 [inline]  __x64_sys_mount\u002B0x27f/0x300 fs/namespace.c:3568  do_syscall_x64 arch/x86/entry/common.c:50 [inline]  do_syscall_64\u002B0x35/0xb0 arch/x86/entry/common.c:80  entry_SYSCALL_64_after_hwframe\u002B0x63/0xcd  [...]  \u003C/TASK\u003E  The buggy address belongs to the physical page: page:ffffea0001f8d400 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x7e350 head:ffffea0001f8d400 order:3 compound_mapcount:0 compound_pincount:0 flags: 0xfff00000010200(slab|head|node=0|zone=1|lastcpupid=0x7ff) raw: 00fff00000010200 0000000000000000 dead000000000122 ffff888011842140 raw: 0000000000000000 0000000000040004 00000001ffffffff 0000000000000000 page dumped because: kasan: bad access detected Memory state around the buggy address:  ffff88807e351f00: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc  ffff88807e351f80: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc \u003Effff88807e352000: fa fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb                       ^  ffff88807e352080: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb  ffff88807e352100: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ==================================================================  Kernel will loads $MFT/$DATA\u0027s first mft record in ntfs_read_inode_mount().  Yet the problem is that after loading, kernel doesn\u0027t check whether attrs_offset field is a valid value.  To be more specific, if attrs_offset field is larger than bytes_allocated field, then it may trigger the out-of-bounds read bug(reported as use-after-free bug) in ntfs_attr_find(), when kernel tries to access the corresponding mft record\u0027s attribute.  This patch solves it by adding the sanity check between attrs_offset field and bytes_allocated field, after loading the first mft record.",
  "published": "2025-05-01T15:15:59Z",
  "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.00217,
  "epssPercentile": 0.12221,
  "priority": "High",
  "priorityTier": 3,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "fixes": [
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 12.15 (bookworm)",
      "fixedVersion": "6.0.10-1",
      "fix": "DEBIAN-CVE-2022-49763",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-49763",
      "released": "2025-05-01T15:15:59Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 13.5 (trixie)",
      "fixedVersion": "6.0.10-1",
      "fix": "DEBIAN-CVE-2022-49763",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-49763",
      "released": "2025-05-01T15:15:59Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 14",
      "fixedVersion": "6.0.10-1",
      "fix": "DEBIAN-CVE-2022-49763",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-49763",
      "released": "2025-05-01T15:15:59Z"
    }
  ],
  "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"
  }
}