Kernel-memory disclosure via unchecked NTFS filename length
Published Aug 28, 2024 · Updated Nov 3, 2025
An out-of-bounds read in Linux kernel NTFS3 through 6.8.0 allows physically proximate attackers to read kernel memory. The directory iterator passes an unvalidated $FILE_NAME character count to ntfs_utf16_to_nls(), which reads beyond the allocated attribute. Exploitation requires mounting and listing an attacker-modified NTFS image, with exposure depending on permission to mount removable media.
Summary
What happened
An out-of-bounds read in Linux kernel NTFS3 through 6.8.0 allows physically proximate attackers to read kernel memory. The directory iterator passes an unvalidated $FILE_NAME character count to ntfs_utf16_to_nls(), which reads beyond the allocated attribute. Exploitation requires mounting and listing an attacker-modified NTFS image, with exposure depending on permission to mount removable media.
The record
- CVE
- CVE-2023-45896
- Published
- Aug 28, 2024
- Updated
- Nov 3, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-276, CWE-125, T1005
- Attack vector
- physical
- Privileges
- Unavailable
Timeline
How it unfolded
- Aug 28, 2024CVE publishedPublication date reported by the CVE source.
- Nov 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo