{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90199 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90199 is a high-severity vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-90199 and fix it if it is affected.\n\nWhat it is: CVE-2026-90199 is a high-severity vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-90199 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-90199/ (Markdown: https://insights.sbomify.com/CVE-2026-90199/index.md)","id":"CVE-2026-90199","markdown":"https://insights.sbomify.com/CVE-2026-90199/index.md","name":"CVE-2026-90199","record":{"aliases":["AZL-102422","BELL-CVE-2026-90199","DEBIAN-CVE-2026-90199","GHSA-6r4v-32r5-fpv2","UBUNTU-CVE-2026-90199"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel NTFS3","requires_auth":"none","summary":"A malformed NTFS3 disk image can trigger an integer overflow in the kernel, leading to a denial of service.","user_interaction":"required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"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's 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]","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"fs/ntfs3: reject out-of-range evcn in mi_enum_attr()","id":"CVE-2026-90199","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"fs/ntfs3: fix integer overflow in MFT cluster validation","id":"CVE-2026-90200"},"packages":[],"prev":{"headline":"ALSA: core: Fix use-after-free in snd_card_do_free()","id":"CVE-2026-90198"},"products":["Linux"],"published":"2026-09-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A malformed NTFS3 disk image can trigger an integer overflow in the kernel, leading to a denial of service.","url":"https://insights.sbomify.com/CVE-2026-90199/"}