Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-90199fs/ntfs3: reject out-of-range evcn in mi_enum_attr()

Description

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. [[email protected]: fixed evcn check]

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 32 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-90199, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVDNVD · Received3.1High7.8CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.17% · top 93% of all CVEs (14 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 013ff63b649475f0ee134e2c8d0c8e65284ede50 – < 0441e34ce098c19185a7b52c5b8b89a8a5b26888
    • affected 013ff63b649475f0ee134e2c8d0c8e65284ede50 – < 7ab69cef49ebdfee288287d62641b24ab1445ecc
    • affected 013ff63b649475f0ee134e2c8d0c8e65284ede50 – < ce9a619c432b9a4044fee115c5483fbed946c131
    • affected 013ff63b649475f0ee134e2c8d0c8e65284ede50 – < 2b9a0e57bfd365e2096706b19ae34dce3b4a884b
    • affected 013ff63b649475f0ee134e2c8d0c8e65284ede50 – < 20fd9f64c0050658f2031e6bd5d552c6f0c8f7e3
    • affected a7accf181a4709a6e380360372150cc4a1b6b89a
    • affected 3dfd727873c3e8da74a2e3907120ff052c5f0bcc
    • affected 1d7dd485108d4f633b543c9c14071cc325b68ae5
    • affected 5.15.209 – < 5.16
    • affected 6.1.115 – < 6.2
    • affected 6.5.11 – < 6.6
  • Linux · Linux

    • affected 6.6
    • unaffected < 6.6
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-90199 badge
[![CVE-2026-90199](https://cveledger.app/badge/CVE-2026-90199.svg)](https://cveledger.app/cve/CVE-2026-90199)

Record last updated .