Kernel-memory disclosure via premature NTFS attribute dereference
Published Feb 26, 2023 · Updated May 5, 2025
Out-of-bounds read in the Linux kernel NTFS driver 6.0.8 allows local users to disclose kernel memory through a crafted NTFS image. ntfs_attr_find dereferences an attribute record's name offset and length before confirming that the record header lies within the MFT record bounds. Exploitation requires local access sufficient to mount the crafted filesystem and can expose kernel memory or crash the system.
Summary
What happened
Out-of-bounds read in the Linux kernel NTFS driver 6.0.8 allows local users to disclose kernel memory through a crafted NTFS image. ntfs_attr_find dereferences an attribute record's name offset and length before confirming that the record header lies within the MFT record bounds. Exploitation requires local access sufficient to mount the crafted filesystem and can expose kernel memory or crash the system.
The record
- CVE
- CVE-2023-26607
- Published
- Feb 26, 2023
- Updated
- May 5, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-125
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Feb 26, 2023CVE publishedPublication date reported by the CVE source.
- May 5, 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.
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
- KASAN ntfs_attr_find reproducerproof of concept · demonstrated
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