{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2023-54077",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2023-54077"
  ],
  "published": "2025-12-24T13:03:53Z",
  "summary": "fs/ntfs3: Fix memory leak if ntfs_read_mft failed",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nfs/ntfs3: Fix memory leak if ntfs_read_mft failed\n\nLabel ATTR_ROOT in ntfs_read_mft() sets is_root = true and\nni->ni_flags |= NI_FLAG_DIR, then next attr will goto label ATTR_ALLOC\nand alloc ni->dir.alloc_run. However two states are not always\nconsistent and can make memory leak.\n\n 1) attr_name in ATTR_ROOT does not fit the condition it will set\n is_root = true but NI_FLAG_DIR is not set.\n 2) next attr_name in ATTR_ALLOC fits the condition and alloc\n ni->dir.alloc_run\n 3) in cleanup function ni_clear(), when NI_FLAG_DIR is set, it frees\n ni->dir.alloc_run, otherwise it frees ni->file.run\n 4) because NI_FLAG_DIR is not set in this case, ni->dir.alloc_run is\n leaked as kmemleak reported:\n\nunreferenced object 0xffff888003bc5480 (size 64):\n  backtrace:\n    [<000000003d42e6b0>] __kmalloc_node+0x4e/0x1c0\n    [<00000000d8e19b8a>] kvmalloc_node+0x39/0x1f0\n    [<00000000fc3eb5b8>] run_add_entry+0x18a/0xa40 [ntfs3]\n    [<0000000011c9f978>] run_unpack+0x75d/0x8e0 [ntfs3]\n    [<00000000e7cf1819>] run_unpack_ex+0xbc/0x500 [ntfs3]\n    [<00000000bbf0a43d>] ntfs_iget5+0xb25/0x2dd0 [ntfs3]\n    [<00000000a6e50693>] ntfs_fill_super+0x218d/0x3580 [ntfs3]\n    [<00000000b9170608>] get_tree_bdev+0x3fb/0x710\n    [<000000004833798a>] vfs_get_tree+0x8e/0x280\n    [<000000006e20b8e6>] path_mount+0xf3c/0x1930\n    [<000000007bf15a5f>] do_mount+0xf3/0x110\n    ...\n\nFix this by always setting is_root and NI_FLAG_DIR together.",
  "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-54077"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/3030f2b9b3329db3948c1a145a5493ca6f617d50"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/1bc6bb657dfb0ab3b94ef6d477ca241bf7b6ec06"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/93bf79f989688852deade1550fb478b0a4d8daa8"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/3bb0d3eb475f01744ce6d6e998dfbd80220852a1"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/bfa434c60157c9793e9b12c9b68ade02aff9f803"
    }
  ],
  "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 vulnerable code is the on-disk MFT record parser, reached via ntfs_fill_super()/ntfs_iget5() when an attacker-supplied NTFS volume is mounted, requiring local presentation of the image (USB stick, loop device, disk image) rather than network access.\nAC:L - The inconsistent is_root/NI_FLAG_DIR state is produced deterministically by attacker-controlled on-disk structures \u2014 an $INDEX_ROOT attribute named other than $I30 (or in a record without RECORD_FLAG_DIR) followed by an $INDEX_ALLOCATION attribute \u2014 with no race and no reliance on memory layout the attacker cannot influence.\nPR:N - The attacker only has to supply the malicious filesystem image and needs no account or privileges on the target system; the mount is performed by the victim or by an automounter such as udisks2.\nUI:R - Exploitation requires someone on the target to mount the crafted NTFS volume, e.g. inserting the attacker's USB device or opening the supplied image.\nS:U - The corruption and leak are confined to kernel memory managed by the same kernel security authority; no VM, IOMMU, or sandbox boundary is crossed.\nC:H - Because ni->dir and ni->file share a union, dir.alloc_run.allocated aliases file.run.runs, leaving the file's runs_tree with a bogus base pointer and (for the $MFT case) an enormous count, so run_lookup()/run_lookup_entry() perform out-of-bounds reads of kernel memory that influence returned file data.\nI:H - The same union aliasing lets run_add_entry() store r->vcn/lcn/len through the corrupted runs_tree base, and run_close() in ni_clear() calls kvfree() on a non-pointer value, corrupting slab/page-allocator state \u2014 memory corruption leverageable for control-flow hijacking.\nA:H - Every affected inode leaks its kvmalloc'ed run array unboundedly (kmemleak-confirmed), and on default configs the aliased ni->file.run.runs causes an invalid kvfree()/wild-pointer dereference at inode eviction or unmount, producing a kernel oops."
    }
  }
}