CVE-2026-46062: ntfs3: fix integer overflow in run_unpack() volume boundary check
In the Linux kernel, the following vulnerability has been resolved:
ntfs3: fix integer overflow in run_unpack() volume boundary check
The volume boundary check `lcn + len > sbi->used.bitmap.nbits` uses raw
addition which can wrap around for large lcn and len values, bypassing
the validation. Use check_add_overflow() as is already done for the
adjacent prev_lcn + dlcn and vcn64 + len checks added by commit
3ac37e100385 ("ntfs3: Fix integer overflow in run_unpack()").
Found by fuzzing with a source-patched harness (LibAFL + QEMU).
Security readout for executives and security teams
Plain-English summary
A flaw in Linux’s NTFS3 filesystem driver can let specially crafted filesystem data bypass a volume-boundary check because an integer calculation wraps around. Exploitation requires local interaction with NTFS content and user action, but the supplied CVSS assessment indicates potentially severe confidentiality, integrity, and availability impact.
Executive priority
Prioritize patching endpoints, analysis systems, and servers that handle removable or externally supplied NTFS content. Treat broad emergency action as context-dependent because exploitation requires local interaction and the sources show no active exploitation. Maintain normal expedited remediation for a high-severity kernel filesystem flaw.
Technical view
In ntfs3 run_unpack(), the expression lcn + len can overflow before comparison with the volume bitmap size, allowing invalid run data to evade validation. The kernel fix replaces raw addition with check_add_overflow(), consistent with nearby checks. The issue was found through LibAFL and QEMU fuzzing.
Likely exposure
Exposure centers on Linux systems using the NTFS3 driver to process untrusted or attacker-influenced NTFS volumes or images. The supplied record lists multiple affected kernel releases from 5.15 through 7.1, but its version data is irregular; confirm status using the relevant distribution or kernel stable branch.
Exploitation context
The CVSS vector is local, low complexity, requires no privileges, and requires user interaction. The source bundle marks the CVE as absent from KEV and provides no evidence of active exploitation or a public weaponized exploit. Discovery occurred through fuzzing with a source-patched harness.
Researcher notes
The security boundary failure is an unchecked unsigned addition in a volume-limit comparison. Review should focus on whether lcn plus len is rejected on overflow and whether downstream run processing becomes reachable. The supplied sources do not establish the precise resulting corruption primitive, practical exploitability, or affected distribution package versions.
Mitigation direction
Update to a vendor-supported kernel containing the applicable referenced stable fix.
Consult the Linux distribution’s advisory to map packaged kernel versions accurately.
Restrict mounting or processing of untrusted NTFS media and filesystem images until patched.
Where operationally feasible, disable unnecessary NTFS3 usage pending remediation.
Validation and detection
Inventory systems that load or can load the ntfs3 kernel module.
Record running kernel and distribution package versions on exposed systems.
Confirm the installed kernel includes the applicable stable fix or vendor backport.
Review workflows accepting removable media or externally supplied NTFS images.
After updating, reboot and verify the patched kernel is running.
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-2026-46062 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
0ADP providers
8Source 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.