CVE-2021-35268
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn NTFS-3G versions < 2021.8.22, when a specially crafted NTFS inode is loaded in the function ntfs_inode_real_open, a heap buffer overflow can occur allowing for code execution and escalation of privileges.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is a heap buffer overflow vulnerability in the NTFS-3G driver where loading a specially crafted NTFS inode via the ntfs_inode_real_open function causes overflow, potentially allowing local attackers to achieve code execution and privilege escalation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 9.0= 10.0= 11.0= 33= 35< 2021.8.22CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if NTFS-3G is installedRun 'dpkg -l | grep ntfs-3g' on Debian or 'rpm -qa | grep ntfs-3g' on Fedora to list installed NTFS-3G packagesAffected if No NTFS-3G package is found, then the system is not vulnerable via this vector
-
Determine installed NTFS-3G version on DebianRun 'dpkg -l ntfs-3g' and note the version number displayed (e.g., 1:2017.3.23AR.3-13)Affected if The version is earlier than 2021.8.22 (for Tuxera builds) or matches Debian versions 9.0, 10.0, or 11.0 package versions which predate the fix
-
Determine installed NTFS-3G version on FedoraRun 'rpm -qi ntfs-3g' and note the Version and Release fieldsAffected if The version is 2021.8.22 or earlier, matching Fedora 33 or 35 packages
-
Check NTFS-3G binary version directlyRun 'ntfs-3g --version' to display the exact version string of the ntfs-3g binaryAffected if The version output shows a number lower than 2021.8.22
-
Verify if NTFS volumes have been mountedRun 'mount | grep -i ntfs' to list any currently mounted NTFS partitions, or check /etc/fstab for NTFS entriesAffected if NTFS partitions are mounted using NTFS-3G - the vulnerable code path (ntfs_inode_real_open) is invoked when accessing NTFS filesystems
A system is affected if NTFS-3G is installed with a version earlier than 2021.8.22 AND NTFS volumes are or can be mounted using this driver, as the heap overflow triggers when opening specially crafted NTFS inodes.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2021.8.22
Upgrade NTFS-3G to version 2021.8.22 or later to patch the heap overflow vulnerability in ntfs_inode_real_open.
NTFS-3G version 2021.8.22 or later
- 1. Check current NTFS-3G version: dpkg -l | grep ntfs-3g (Debian) or rpm -q ntfs-3g (Fedora)
- 2. Update package repository metadata: apt update (Debian) or dnf check-update (Fedora)
- 3. Upgrade NTFS-3G package: apt install ntfs-3g (Debian) or dnf update ntfs-3g (Fedora)
- 4. Verify installed version is 2021.8.22 or later: ntfs-3g --version
- 5. If applicable, reboot system or remount any NTFS filesystems to ensure the updated library is loaded
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-35268 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-35268 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data