CVE-2026-90199

Vulnérabilité élevée dans Linux (Linux)

CVSS 7.8 · Élevée
EPSS 0.2%
Linux•Linux•Versions : <=6.12.*, a7accf181a4709a6e380360372150cc4a1b6b89a, 3dfd727873c3e8da74a2e3907120ff052c5f0bcc, 0, 6.1.115, 6.5.11, 6.18.52, 013ff63b649475f0ee134e2c8d0c8e65284ede50, <6.6, 5.15.209, <20fd9f64c0050658f2031e6bd5d552c6f0c8f7e3, <=6.6.*, <0441e34ce098c19185a7b52c5b8b89a8a5b26888, 6.6.157, <ce9a619c432b9a4044fee115c5483fbed946c131, 6.6, 7.2.6, <5.16, <=6.18.*, 1d7dd485108d4f633b543c9c14071cc325b68ae5, <6.2, 6.12.110, <=7.2.*, <=*, <7ab69cef49ebdfee288287d62641b24ab1445ecc, <2b9a0e57bfd365e2096706b19ae34dce3b4a884b, 7.3

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. [almaz.alexandrovich@paragon-software.com: fixed evcn check]

Gravité et risque d'exploitation

CVE-2026-90199 obtient un score CVSS de 7.8/10, soit une gravité élevée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.17 %, ce qui la place devant 6.4 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.12.*, a7accf181a4709a6e380360372150cc4a1b6b89a, 3dfd727873c3e8da74a2e3907120ff052c5f0bcc, 0, 6.1.115, 6.5.11, 6.18.52, 013ff63b649475f0ee134e2c8d0c8e65284ede50, <6.6, 5.15.209, <20fd9f64c0050658f2031e6bd5d552c6f0c8f7e3, <=6.6.*, <0441e34ce098c19185a7b52c5b8b89a8a5b26888, 6.6.157, <ce9a619c432b9a4044fee115c5483fbed946c131, 6.6, 7.2.6, <5.16, <=6.18.*, 1d7dd485108d4f633b543c9c14071cc325b68ae5, <6.2, 6.12.110, <=7.2.*, <=*, <7ab69cef49ebdfee288287d62641b24ab1445ecc, <2b9a0e57bfd365e2096706b19ae34dce3b4a884b, 7.3) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références