{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2023-53988",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2023-53988"
  ],
  "published": "2025-12-24T10:57:20Z",
  "summary": "fs/ntfs3: Fix slab-out-of-bounds read in hdr_delete_de()",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nfs/ntfs3: Fix slab-out-of-bounds read in hdr_delete_de()\n\nHere is a BUG report from syzbot:\n\nBUG: KASAN: slab-out-of-bounds in hdr_delete_de+0xe0/0x150 fs/ntfs3/index.c:806\nRead of size 16842960 at addr ffff888079cc0600 by task syz-executor934/3631\n\nCall Trace:\n memmove+0x25/0x60 mm/kasan/shadow.c:54\n hdr_delete_de+0xe0/0x150 fs/ntfs3/index.c:806\n indx_delete_entry+0x74f/0x3670 fs/ntfs3/index.c:2193\n ni_remove_name+0x27a/0x980 fs/ntfs3/frecord.c:2910\n ntfs_unlink_inode+0x3d4/0x720 fs/ntfs3/inode.c:1712\n ntfs_rename+0x41a/0xcb0 fs/ntfs3/namei.c:276\n\nBefore using the meta-data in struct INDEX_HDR, we need to\ncheck index header valid or not. Otherwise, the corruptedi\n(or malicious) fs image can cause out-of-bounds access which\ncould make kernel panic.",
  "severity": [
    {
      "type": "CVSS_V3",
      "score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H"
    }
  ],
  "affected": [
    {
      "package": {
        "ecosystem": "Raspberry Pi OS:12",
        "name": "linux"
      },
      "versions": [
        "1:6.1.21-1+rpt1"
      ],
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-image-6.1.0-rpi1-rpi-v6",
            "binary_version": "1:6.1.21-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi1-rpi-v7",
            "binary_version": "1:6.1.21-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi1-rpi-v7l",
            "binary_version": "1:6.1.21-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi1-rpi-v8",
            "binary_version": "1:6.1.21-1+rpt1"
          }
        ]
      },
      "database_specific": {
        "per_version": {
          "1:6.1.21-1+rpt1": {
            "linux_commit": "0afb5e98488aed7017b9bf321b575d0177feb7ed",
            "upstream_version": "6.1.21",
            "assessment": "commit ancestry (strak rule)",
            "upstream_fixed": "6.1.28"
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2023-53988"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/c58ea97aa94f033ee64a8cb6587d84a9849b6216"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/9163a5b4ed290da4a7d23fa92533e0e81fd0166e"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/114204d25e1dffdd3a0c1cfbba219afd344f4b4f"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/4a034ece7e2877673d9085d6e7ed45e6ee40b761"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/ab84eee4c7ab929996602eda7832854c35a6dda2"
    }
  ],
  "database_specific": {
    "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git",
    "upstream_modified": "2026-08-05T11:24:39Z",
    "severity": {
      "source": "kernel CNA",
      "cvss_v3_score": 7.8,
      "cvss_v3_severity": "High",
      "scenario": "AV:L - The malicious INDEX_HDR fields arrive via a mounted NTFS volume (USB stick, loop-mounted image, NBD/VM disk), and the bug is triggered through a local rename()/unlink() syscall. No network protocol is involved, and physical access is not required since the image can be delivered as a file, so Local rather than Physical.\nAC:L - The attacker fully controls hdr->used, hdr->de_off and the entry size in the crafted image, so the oversized memmove length is chosen deterministically and fires on the first rename/unlink of the crafted directory entry. There is no race, no timing window, and no dependence on memory layout to reach the corruption.\nPR:N - The attacker needs no account or privilege on the target \u2014 they merely supply the crafted NTFS image or removable device, matching the established scoring for this ntfs3 hostile-image class. Once the volume is mounted, plain directory-write access is all that is needed to reach ntfs_rename().\nUI:R - A victim (or an automount daemon acting on their behalf, e.g. udisks2 on USB insertion) must mount the attacker's NTFS volume, and a rename/unlink must be performed against it. This is the standard user-interaction requirement for crafted-filesystem-image bugs.\nS:U - The out-of-bounds access corrupts kernel slab memory within the same kernel security authority. No VM, sandbox, or IOMMU boundary is crossed.\nC:H - The memmove reads up to ~16 MB past the slab object, and the callers immediately persist the buffer back to the volume via indx_write()/mi_write(), writing adjacent kernel heap contents onto the attacker's image for later retrieval. That is a large, effectively unbounded kernel-memory disclosure primitive.\nI:H - The same memmove writes that attacker-influenced multi-megabyte length starting inside the index buffer, overwriting arbitrary adjacent slab objects with shifted heap data. Heap corruption of this magnitude is leverageable for control-flow hijack and privilege escalation.\nA:H - An unbounded ~16 MB memmove past a ~1 KB kmalloc object destroys allocator metadata and touches unmapped memory, producing the KASAN-reported fault and a kernel panic. The commit message explicitly states the corrupted image \"could make kernel panic.\""
    }
  }
}