{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90200 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-90200 is a 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-90200 and fix it if it is affected.\n\nWhat it is: CVE-2026-90200 is a 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-90200 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-90200/ (Markdown: https://insights.sbomify.com/CVE-2026-90200/index.md)","id":"CVE-2026-90200","markdown":"https://insights.sbomify.com/CVE-2026-90200/index.md","name":"CVE-2026-90200","record":{"aliases":["AZL-102926","BELL-CVE-2026-90200","DEBIAN-CVE-2026-90200","GHSA-h945-5whj-h8mc","UBUNTU-CVE-2026-90200"],"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":"An integer overflow in the Linux kernel NTFS3 driver allows bypassing validation, leading to mount failures and denial of service when processing malformed boot sectors.","user_interaction":"required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nfs/ntfs3: fix integer overflow in MFT cluster validation\n\nIn ntfs_init_from_boot(), the boot sector's MFT cluster numbers are\nvalidated against the volume size with:\n\n\tif (mlcn  * sct_per_clst \u003e= sectors ||\n\t    mlcn2 * sct_per_clst \u003e= sectors)\n\t\tgoto out;\n\nmlcn and mlcn2 are u64 fields read directly from the boot sector.\nsct_per_clst is bounded above by 4096 (true_sectors_per_clst() plus\nthe is_power_of_2() check below it), but the multiplication is done\nin u64 and wraps when mlcn (or mlcn2) is large enough -- e.g. mlcn\nnear 2^62 with sct_per_clst == 4 wraps to 0, which compares below\nany non-zero 'sectors', so the check is bypassed and the malformed\nrecord is accepted.\n\nThe accepted mlcn is then used unchanged in\n\n\tsbi-\u003emft.lbo = mlcn \u003c\u003c cluster_bits;\n\nIn practice the resulting reads fail at the block layer (sb_bread()\nreturns NULL via grow_buffers()'s check_mul_overflow() guard), so\ntoday this manifests as mount failing in odd places rather than as\nsomething more dangerous, but the validation step is still wrong\nand there is no reason for callers to rely on the block layer to\ncatch a value that should never have been accepted in the first\nplace.\n\nUse check_mul_overflow() to compute the two sector positions and\nfail the mount if either multiplication wraps; this preserves the\nexisting semantics (mlcn * sct_per_clst \u003e= sectors) instead of\nswitching to division (mlcn \u003e= sectors / sct_per_clst), which\nwould tighten the check at edge cases where 'sectors' is not a\nmultiple of sct_per_clst.  The check_*_overflow() style is the\none ntfs3 already uses for similar on-disk arithmetic in\nfs/ntfs3/run.c.","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: fix integer overflow in MFT cluster validation","id":"CVE-2026-90200","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":"net: page_pool: fix UAF in __page_pool_release_netmem_dma on xa_cmpxchg race","id":"CVE-2026-90201"},"packages":[],"prev":{"headline":"fs/ntfs3: reject out-of-range evcn in mi_enum_attr()","id":"CVE-2026-90199"},"products":["Linux"],"published":"2026-09-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"An integer overflow in the Linux kernel NTFS3 driver allows bypassing validation, leading to mount failures and denial of service when processing malformed boot sectors.","url":"https://insights.sbomify.com/CVE-2026-90200/"}