CVE-2024-52560 (GCVE-0-2024-52560)
Vulnerability from cvelistv5
Published
2025-02-27 02:18
Modified
2026-08-05 11:43
Severity ?
7.8 (High) - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Summary
In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: Mark inode as bad as soon as error detected in mi_enum_attr() Extended the `mi_enum_attr()` function interface with an additional parameter, `struct ntfs_inode *ni`, to allow marking the inode as bad as soon as an error is detected.
References
Impacted products
Vendor Product Version
Linux Linux Version: 4534a70b7056fd4b9a1c6db5a4ce3c98546b291e
Version: 4534a70b7056fd4b9a1c6db5a4ce3c98546b291e
 Create a notification for this product.
Show details on NVD website

To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "fs/ntfs3/attrib.c",
            "fs/ntfs3/frecord.c",
            "fs/ntfs3/ntfs_fs.h",
            "fs/ntfs3/record.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "d9c699f2c4dc174940ffe8600b20c267897da155",
              "status": "affected",
              "version": "4534a70b7056fd4b9a1c6db5a4ce3c98546b291e",
              "versionType": "git"
            },
            {
              "lessThan": "2afd4d267e6dbaec8d3ccd4f5396cb84bc67aa2e",
              "status": "affected",
              "version": "4534a70b7056fd4b9a1c6db5a4ce3c98546b291e",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "fs/ntfs3/attrib.c",
            "fs/ntfs3/frecord.c",
            "fs/ntfs3/ntfs_fs.h",
            "fs/ntfs3/record.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "5.15"
            },
            {
              "lessThan": "5.15",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.13.*",
              "status": "unaffected",
              "version": "6.13.4",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.14",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.13.4",
                  "versionStartIncluding": "5.15",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.14",
                  "versionStartIncluding": "5.15",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nfs/ntfs3: Mark inode as bad as soon as error detected in mi_enum_attr()\n\nExtended the `mi_enum_attr()` function interface with an additional\nparameter, `struct ntfs_inode *ni`, to allow marking the inode\nas bad as soon as an error is detected."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 7.8,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:L - The corrupt MFT record arrives on a locally attached or loop-backed block device and is triggered through ordinary local path resolution and file operations (the syzbot trace is `__do_sys_mount` \u2192 `user_path_at` \u2192 `path_lookupat` \u2192 `step_into` \u2192 `pick_link`); no network protocol or remote peer feeds `mi_enum_attr()`.\nAC:L - The attacker authors the entire on-disk MFT record, so which validation check in `mi_enum_attr()` fails and where enumeration silently truncates is fully deterministic, and the stale `i_dir_seq`/`i_link` union value is influenced by ordinary directory operations the attacker performs; no race and no memory-layout condition lies outside the attacker\u0027s control, and the trigger is repeatable at will.\nPR:L - ntfs3 registers without `FS_USERNS_MOUNT`, but udisks2 loop-setup/filesystem-mount and removable-media automount hand the mount to any active local session on desktop, kiosk, NAS and media-appliance deployments, and ntfs3 mounts default to permissive uid/gid/fmask/dmask; once mounted, an unprivileged user reaches the fault through plain pathname resolution and truncate/write with no capability check anywhere on the path.\nUI:N - The attacker supplies the crafted image, gets it mounted via automount/udisks2, and then performs the triggering lookup and `attr_set_size`-inducing write itself; no action by any other user or administrator is required.\nS:U - The wild-pointer dereference, the inode/dentry type desynchronization, and the on-disk metadata damage all occur within the kernel\u0027s own security authority; no VM, IOMMU, or sandbox boundary is crossed.\nC:H - `pick_link()` dereferences `inode-\u003ei_link`, which ntfs3 never sets and which is a union aliasing `i_pipe`/`i_cdev`/`i_dir_seq` \u2014 an attacker-influenced value that path resolution then reads as a NUL-terminated string and consumes as a path, giving a steerable kernel read primitive on configurations without KASAN; the freed-but-still-referenced MFT records from `ni_write_inode()` additionally cross-link attributes and clusters between unrelated files.\nI:H - The bogus symlink body redirects path resolution to attacker-chosen targets, and the write path corrupts persistent state \u2014 `ni_write_inode()` calls `clear_rec_inuse()` plus `ntfs_mark_rec_free()` on records that still hold live attributes, while `mi_insert_attr()` `memmove`/`memset`s a new attribute over live attribute bytes at `rec-\u003eused - 8` and bumps `rec-\u003eused`, with both written back to disk and re-parsed later.\nA:H - syzbot reproduced a general protection fault / KASAN null-ptr-deref at `pick_link+0x51c` (fs/namei.c:1864) five times across 6.12-rc6 through 6.15, oopsing the task mid-path-resolution \u2014 a full panic on the many embedded and hardened deployments running `panic_on_oops`, and otherwise a tainted kernel with leaked path/mount references and a volume flagged `NTFS_DIRTY_ERROR`."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-05T11:43:18.694Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/d9c699f2c4dc174940ffe8600b20c267897da155"
        },
        {
          "url": "https://git.kernel.org/stable/c/2afd4d267e6dbaec8d3ccd4f5396cb84bc67aa2e"
        }
      ],
      "title": "fs/ntfs3: Mark inode as bad as soon as error detected in mi_enum_attr()",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2024-52560",
    "datePublished": "2025-02-27T02:18:07.676Z",
    "dateReserved": "2025-02-27T02:16:34.069Z",
    "dateUpdated": "2026-08-05T11:43:18.694Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.