Privileged code execution via malformed inode metadata
Published Sep 7, 2021 · Updated Jul 9, 2026
Heap buffer overflow in NTFS-3G before 2021.8.22 allows local users to execute privileged code by loading a crafted NTFS inode. The ntfs_inode_real_open function inadequately validates inode metadata and writes beyond a heap allocation while opening the crafted inode. Exploitation requires local access to a setuid-root ntfs-3g binary, or physical access to insert storage into a system configured to process it.
Summary
What happened
Heap buffer overflow in NTFS-3G before 2021.8.22 allows local users to execute privileged code by loading a crafted NTFS inode. The ntfs_inode_real_open function inadequately validates inode metadata and writes beyond a heap allocation while opening the crafted inode. Exploitation requires local access to a setuid-root ntfs-3g binary, or physical access to insert storage into a system configured to process it.
The record
- CVE
- CVE-2021-35268
- Published
- Sep 7, 2021
- Updated
- Jul 9, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-20, CWE-787, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 7, 2021CVE publishedPublication date reported by the CVE source.
- Jul 9, 2026Record 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
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