FKIE_CVE-2026-90199
Vulnerability from fkie_nvd - Published: 2026-09-17 17:17 - Updated: 2026-09-18 18:17
Severity
Summary
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]
References
Impacted products
| Vendor | Product | Version |
|---|
{
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"fs/ntfs3/record.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "0441e34ce098c19185a7b52c5b8b89a8a5b26888",
"status": "affected",
"version": "013ff63b649475f0ee134e2c8d0c8e65284ede50",
"versionType": "git"
},
{
"lessThan": "7ab69cef49ebdfee288287d62641b24ab1445ecc",
"status": "affected",
"version": "013ff63b649475f0ee134e2c8d0c8e65284ede50",
"versionType": "git"
},
{
"lessThan": "ce9a619c432b9a4044fee115c5483fbed946c131",
"status": "affected",
"version": "013ff63b649475f0ee134e2c8d0c8e65284ede50",
"versionType": "git"
},
{
"lessThan": "2b9a0e57bfd365e2096706b19ae34dce3b4a884b",
"status": "affected",
"version": "013ff63b649475f0ee134e2c8d0c8e65284ede50",
"versionType": "git"
},
{
"lessThan": "20fd9f64c0050658f2031e6bd5d552c6f0c8f7e3",
"status": "affected",
"version": "013ff63b649475f0ee134e2c8d0c8e65284ede50",
"versionType": "git"
},
{
"status": "affected",
"version": "a7accf181a4709a6e380360372150cc4a1b6b89a",
"versionType": "git"
},
{
"status": "affected",
"version": "3dfd727873c3e8da74a2e3907120ff052c5f0bcc",
"versionType": "git"
},
{
"status": "affected",
"version": "1d7dd485108d4f633b543c9c14071cc325b68ae5",
"versionType": "git"
},
{
"lessThan": "5.16",
"status": "affected",
"version": "5.15.209",
"versionType": "semver"
},
{
"lessThan": "6.2",
"status": "affected",
"version": "6.1.115",
"versionType": "semver"
},
{
"lessThan": "6.6",
"status": "affected",
"version": "6.5.11",
"versionType": "semver"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"fs/ntfs3/record.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.6"
},
{
"lessThan": "6.6",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.6.*",
"status": "unaffected",
"version": "6.6.157",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.12.*",
"status": "unaffected",
"version": "6.12.110",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.52",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.2.*",
"status": "unaffected",
"version": "7.2.6",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.3-rc1",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nfs/ntfs3: reject out-of-range evcn in mi_enum_attr()\n\nIn mi_enum_attr(), the start/end VCN validation for non-resident\nattributes is:\n\n\tif (svcn \u003e evcn + 1) goto out;\n\nWhen evcn is U64_MAX the \"evcn + 1\" expression wraps to 0 and any svcn\npasses the check. For evcn values close to U64_MAX (but not equal to it)\nthe right-hand side is still a meaningless near-wrap upper bound, so a\nmalformed on-disk attribute with svcn == 0 and evcn near U64_MAX can pass\nmi_enum_attr() unrejected.\n\nVCN (virtual cluster number) is a cluster index, so any valid evcn is\nbounded by the volume\u0027s total cluster count, which ntfs3 holds in\nsbi-\u003eused.bitmap.nbits (set up in ntfs_init_from_boot() before any caller\nof mi_enum_attr() runs). Reject evcn values that fall outside this range.\n\nHowever, an empty non-resident attribute (no allocated clusters) is\nlegitimately encoded with svcn == 0 and evcn == -1 (U64_MAX), e.g. via\nattr-\u003enres.evcn = cpu_to_le64((u64)vcn - 1) with vcn == 0. That sentinel\nmust keep passing, so exclude evcn == U64_MAX from the range check. The\nexisting \"svcn \u003e evcn + 1\" test still tolerates the sentinel (\"0 \u003e 0\" is\nfalse) and continues to require svcn == 0 for it, while the range check\nrejects every other out-of-range evcn and thereby also defuses the\n\"evcn + 1\" wraparound.\n\nsvcn does not need its own bound: once evcn \u003c nbits, \"svcn \u003e evcn + 1\"\nimplies svcn \u003c= nbits.\n\n[almaz.alexandrovich@paragon-software.com: fixed evcn check]"
}
],
"id": "CVE-2026-90199",
"lastModified": "2026-09-18T18:17:45.950",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 7.8,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 1.8,
"impactScore": 5.9,
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"type": "Secondary"
}
]
},
"published": "2026-09-17T17:17:14.790",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/0441e34ce098c19185a7b52c5b8b89a8a5b26888"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/20fd9f64c0050658f2031e6bd5d552c6f0c8f7e3"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/2b9a0e57bfd365e2096706b19ae34dce3b4a884b"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/7ab69cef49ebdfee288287d62641b24ab1445ecc"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/ce9a619c432b9a4044fee115c5483fbed946c131"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Loading…
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.
Loading…