CVE-2026-90199
- Source
- https://cve.org/CVERecord?id=CVE-2026-90199
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-90199.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2026-90199
- Downstream
- Related
- Published
- 2026-09-17T16:07:17Z
- Modified
- 2026-10-08T02:52:23Z
- Severity
-
- 7.8 (High) CVSS_V3 - CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H CVSS Calculator
- Summary
- fs/ntfs3: reject out-of-range evcn in mi_enum_attr()
- Details
-
In the Linux kernel, the following vulnerability has been resolved:
fs/ntfs3: reject out-of-range evcn in mi_enum_attr()
In mi_enum_attr(), the start/end VCN validation for non-resident attributes is:
if (svcn > evcn + 1) goto out;When evcn is U64_MAX the "evcn + 1" expression wraps to 0 and any svcn passes the check. For evcn values close to U64_MAX (but not equal to it) the right-hand side is still a meaningless near-wrap upper bound, so a malformed on-disk attribute with svcn == 0 and evcn near U64_MAX can pass mi_enum_attr() unrejected.
VCN (virtual cluster number) is a cluster index, so any valid evcn is bounded by the volume's total cluster count, which ntfs3 holds in sbi->used.bitmap.nbits (set up in ntfs_init_from_boot() before any caller of mi_enum_attr() runs). Reject evcn values that fall outside this range.
However, an empty non-resident attribute (no allocated clusters) is legitimately encoded with svcn == 0 and evcn == -1 (U64_MAX), e.g. via attr->nres.evcn = cpu_to_le64((u64)vcn - 1) with vcn == 0. That sentinel must keep passing, so exclude evcn == U64_MAX from the range check. The existing "svcn > evcn + 1" test still tolerates the sentinel ("0 > 0" is false) and continues to require svcn == 0 for it, while the range check rejects every other out-of-range evcn and thereby also defuses the "evcn + 1" wraparound.
svcn does not need its own bound: once evcn < nbits, "svcn > evcn + 1" implies svcn <= nbits.
[almaz.alexandrovich@paragon-software.com: fixed evcn check]
- Database specific
{ "cna_assigner": "Linux", "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/90xxx/CVE-2026-90199.json" }- References
-
- https://git.kernel.org/stable/c/0441e34ce098c19185a7b52c5b8b89a8a5b26888
- https://git.kernel.org/stable/c/20fd9f64c0050658f2031e6bd5d552c6f0c8f7e3
- https://git.kernel.org/stable/c/2b9a0e57bfd365e2096706b19ae34dce3b4a884b
- https://git.kernel.org/stable/c/7ab69cef49ebdfee288287d62641b24ab1445ecc
- https://git.kernel.org/stable/c/ce9a619c432b9a4044fee115c5483fbed946c131
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/90xxx/CVE-2026-90199.json
- https://nvd.nist.gov/vuln/detail/CVE-2026-90199
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected packages
Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected ranges
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced013ff63b649475f0ee134e2c8d0c8e65284ede50Fixed0441e34ce098c19185a7b52c5b8b89a8a5b26888Fixed7ab69cef49ebdfee288287d62641b24ab1445eccFixedce9a619c432b9a4044fee115c5483fbed946c131Fixed2b9a0e57bfd365e2096706b19ae34dce3b4a884bFixed20fd9f64c0050658f2031e6bd5d552c6f0c8f7e3
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced5.15.209Fixed5.16
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced6.1.115Fixed6.2
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced6.5.11Fixed6.6
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduceda7accf181a4709a6e380360372150cc4a1b6b89a
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced3dfd727873c3e8da74a2e3907120ff052c5f0bcc
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introduced1d7dd485108d4f633b543c9c14071cc325b68ae5