LiveActive security incident?Get immediate response
CVE Record

CVE-2024-52560: fs/ntfs3: Mark inode as bad as soon as error detected in mi_enum_attr()

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel NTFS3 filesystem bug. The fix makes the kernel mark a damaged NTFS inode as bad immediately after an error is detected. The public record does not provide CVSS, impact detail, or confirmed exploitation, so business urgency depends on whether systems mount NTFS media or images.

Executive priority

Treat as exposure-driven maintenance, not an emergency from current evidence. Patch during normal kernel update cycles, with faster action for systems processing untrusted NTFS media or images.

Technical view

CVE-2024-52560 affects Linux kernel fs/ntfs3 behavior in mi_enum_attr(). The kernel change extends the function interface with struct ntfs_inode *ni so error handling can mark the inode bad immediately. Sources identify Linux as affected and point to stable kernel commits, but do not describe attacker control, crashability, privilege impact, or data exposure.

Likely exposure

Most relevant exposure is Linux systems that mount NTFS filesystems using the in-kernel ntfs3 driver, especially removable media, disk images, forensics, backup, or cross-platform file workflows. The bundle lists affected Linux kernel versions but lacks distro package mapping, so organizations should verify vendor backports.

Exploitation context

CISA KEV is false in the bundle, and no cited source states active exploitation. The available sources do not describe exploit prerequisites, exploitability, or impact beyond corrected NTFS3 error handling.

Researcher notes

The source record is sparse: no CVSS, CWE, exploit status, or impact class is provided. Analysis should stay tied to ntfs3 error handling and the two stable commits. Distro advisories are needed for exact vulnerable and fixed package versions.

Mitigation direction

  • Update Linux kernels through vendor-supported packages including the referenced stable fixes.
  • Check distribution advisories for CVE-2024-52560 backport status.
  • Reduce handling of untrusted NTFS media or images until patched.
  • Prioritize systems that automatically mount removable or user-supplied NTFS filesystems.

Validation and detection

  • Inventory Linux kernel versions and vendor package fix status.
  • Identify hosts using the ntfs3 driver or mounting NTFS filesystems.
  • Confirm kernel changelogs reference CVE-2024-52560 or the stable commits.
  • Review workflows accepting removable drives, uploaded disk images, or forensic NTFS images.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-52560 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
3Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux4534a70b7056fd4b9a1c6db5a4ce3c98546b291e, 4534a70b7056fd4b9a1c6db5a4ce3c98546b291eunaffected
LinuxLinux5.15, 0, 6.13.4, 6.14affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.