{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2024-52560","assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","state":"PUBLISHED","assignerShortName":"Linux","dateReserved":"2025-02-27T02:16:34.069Z","datePublished":"2025-02-27T02:18:07.676Z","dateUpdated":"2026-09-14T11:57:47.206Z"},"containers":{"cna":{"providerMetadata":{"orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux","dateUpdated":"2026-09-14T11:57:47.206Z"},"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":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","baseScore":7.8,"baseSeverity":"HIGH"},"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` → `user_path_at` → `path_lookupat` → `step_into` → `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's 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's own security authority; no VM, IOMMU, or sandbox boundary is crossed.\nC:H - `pick_link()` dereferences `inode->i_link`, which ntfs3 never sets and which is a union aliasing `i_pipe`/`i_cdev`/`i_dir_seq` — 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 — `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->used - 8` and bumps `rec->used`, 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 — 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`."}]}],"affected":[{"product":"Linux","vendor":"Linux","defaultStatus":"unaffected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["fs/ntfs3/attrib.c","fs/ntfs3/frecord.c","fs/ntfs3/ntfs_fs.h","fs/ntfs3/record.c"],"versions":[{"version":"4534a70b7056fd4b9a1c6db5a4ce3c98546b291e","lessThan":"4ff4b6b9e85cfe879773ca78d91b1090a3ce19ac","status":"affected","versionType":"git"},{"version":"4534a70b7056fd4b9a1c6db5a4ce3c98546b291e","lessThan":"acfb75eeb3304d08cbd5b5a8c77379459ec6a04e","status":"affected","versionType":"git"},{"version":"4534a70b7056fd4b9a1c6db5a4ce3c98546b291e","lessThan":"d9c699f2c4dc174940ffe8600b20c267897da155","status":"affected","versionType":"git"},{"version":"4534a70b7056fd4b9a1c6db5a4ce3c98546b291e","lessThan":"2afd4d267e6dbaec8d3ccd4f5396cb84bc67aa2e","status":"affected","versionType":"git"}]},{"product":"Linux","vendor":"Linux","defaultStatus":"affected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["fs/ntfs3/attrib.c","fs/ntfs3/frecord.c","fs/ntfs3/ntfs_fs.h","fs/ntfs3/record.c"],"versions":[{"version":"5.15","status":"affected"},{"version":"0","lessThan":"5.15","status":"unaffected","versionType":"semver"},{"version":"6.6.157","lessThanOrEqual":"6.6.*","status":"unaffected","versionType":"semver"},{"version":"6.12.110","lessThanOrEqual":"6.12.*","status":"unaffected","versionType":"semver"},{"version":"6.13.4","lessThanOrEqual":"6.13.*","status":"unaffected","versionType":"semver"},{"version":"6.14","lessThanOrEqual":"*","status":"unaffected","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.15","versionEndExcluding":"6.6.157"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.15","versionEndExcluding":"6.12.110"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.15","versionEndExcluding":"6.13.4"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.15","versionEndExcluding":"6.14"}]}]}],"references":[{"url":"https://git.kernel.org/stable/c/4ff4b6b9e85cfe879773ca78d91b1090a3ce19ac"},{"url":"https://git.kernel.org/stable/c/acfb75eeb3304d08cbd5b5a8c77379459ec6a04e"},{"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"}}}}