LiveActive security incident?Get immediate response
CVE Record

CVE-2024-38625: fs/ntfs3: Check 'folio' pointer for NULL

In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: Check 'folio' pointer for NULL It can be NULL if bmap is called.

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

Security readout for executives and security teams

Plain-English summary

CVE-2024-38625 is a Linux kernel NTFS3 filesystem bug where code failed to handle a missing memory page object. The public record does not provide CVSS, CWE, confirmed impact, or active exploitation. Treat it as a kernel stability and exposure-management issue for systems using NTFS3, not as a confirmed internet-scale emergency.

Executive priority

Prioritize normal kernel patch governance unless NTFS3 is widely used in the environment or systems process removable or untrusted NTFS media. There is no cited evidence of exploitation, but kernel filesystem bugs deserve timely maintenance because failures can affect system availability.

Technical view

The Linux kernel NTFS3 driver was fixed to check whether a folio pointer is NULL. The record says this can occur when bmap is called. Available sources identify affected Linux kernel versions and stable kernel commits, but do not describe exploitability, privilege requirements, or a concrete security impact.

Likely exposure

Exposure is most plausible on Linux systems running affected kernels where the in-kernel NTFS3 filesystem driver is present and used. Systems that never mount or process NTFS volumes through NTFS3 appear less exposed, but the source data does not define exact operational prerequisites.

Exploitation context

CISA KEV is false, and the provided sources do not report active exploitation, public exploit code, or weaponization. The available evidence supports a fixed kernel bug, but not a confirmed real-world attack scenario.

Researcher notes

The record is thin: no CVSS, CWE, detailed impact, or exploit prerequisites are provided. Analysis should focus on mapping affected kernel lines, confirming whether downstream vendors backported the fix, and validating NTFS3 usage before assigning business risk.

Mitigation direction

  • Apply kernel or distribution updates that include the referenced stable fixes.
  • Check vendor advisories because distribution kernels may backport fixes without changing upstream version numbers.
  • Review whether NTFS3 support is needed on affected systems.
  • Avoid unnecessary mounting of untrusted NTFS media until patched.
  • Track kernel.org stable updates for the affected release line.

Validation and detection

  • Inventory Linux kernel versions across servers, endpoints, and appliances.
  • Identify systems with NTFS3 enabled, loaded, or actively mounting NTFS filesystems.
  • Confirm vendor kernel packages include the referenced upstream fixes or equivalent backports.
  • Review kernel logs for NTFS3-related faults if NTFS volumes are used.
Prepared
Confidence
medium
Sources
5

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-38625 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
2ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux82cae269cfa953032fbb8980a7d554d60fb00b17, 82cae269cfa953032fbb8980a7d554d60fb00b17, 82cae269cfa953032fbb8980a7d554d60fb00b17unaffected
LinuxLinux5.15, 0, 6.6.33, 6.9.4, 6.10affected
Weakness

CWE details

No CWE listed

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