CVE-2025-38707: fs/ntfs3: Add sanity check for file name
In the Linux kernel, the following vulnerability has been resolved:
fs/ntfs3: Add sanity check for file name
The length of the file name should be smaller than the directory entry size.
Security readout for executives and security teams
Plain-English summary
A Linux kernel flaw in the NTFS3 filesystem driver fails to ensure a filename fits within its directory entry. A local, low-privileged attacker may be able to expose sensitive information or crash affected systems. Risk is concentrated on systems that process NTFS filesystems through NTFS3, rather than broadly exposed network services.
Executive priority
Prioritize patching systems that routinely mount removable, uploaded, or otherwise untrusted NTFS content. This is high severity but not supported as an Internet-wide emergency or actively exploited threat. Systems without NTFS3 use are lower priority after exposure is verified.
Technical view
CVE-2025-38707 adds a missing bounds sanity check comparing filename length with NTFS directory-entry size. CVSS 3.1 rates it 7.1 with local, low-complexity, low-privilege access, no user interaction, and high confidentiality and availability impact. The supplied evidence does not identify a CWE or provide enough detail to characterize the exact memory-safety failure.
Likely exposure
Potentially exposed systems run an affected Linux kernel and enable or use the NTFS3 driver, especially when mounting NTFS media or images from less-trusted sources. The supplied affected-version metadata spans Linux 5.15 through 6.17 but is ambiguous about precise fixed boundaries; distribution backports must be checked.
Exploitation context
The CVSS vector describes local, low-privilege exploitation without user interaction. CISA KEV status is false, and the supplied sources provide no evidence of active exploitation or a public exploit. Exposure may still arise when an attacker can introduce or influence an NTFS filesystem processed by NTFS3.
Researcher notes
The record supplies seven stable-kernel fix commits but ambiguous affected-version formatting. Confirm ancestry or distribution backport status rather than relying solely on version strings. No CWE, proof-of-concept status, active-exploitation evidence, or detailed failure mode is supplied. Siemens and Debian references may clarify product-specific applicability.
Mitigation direction
Install a vendor-supported kernel containing the referenced NTFS3 filename sanity check.
Check distribution advisories because kernel fixes are frequently backported without matching upstream version numbers.
Disable or avoid NTFS3 where it is not operationally required.
Restrict mounting of untrusted NTFS media and filesystem images until patched.
Validation and detection
Inventory running kernel and package versions across Linux systems.
Identify hosts where NTFS3 is available, loaded, or used for mounted filesystems.
Compare vendor package status with the referenced stable-kernel fixes and distribution advisories.
Confirm patched kernels are running after installation, including following required reboots.
Review logs for NTFS3 faults or unexpected kernel crashes, without treating their absence as proof of safety.
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-2025-38707 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
1CVSS vectors
3Timeline events
2ADP providers
10Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.