{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-99108 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-99108 is a vulnerability in Linux, published on 28 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-99108 and fix it if it is affected.\n\nWhat it is: CVE-2026-99108 is a vulnerability in Linux, published on 28 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-99108 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-99108/ (Markdown: https://insights.sbomify.com/CVE-2026-99108/index.md)","id":"CVE-2026-99108","markdown":"https://insights.sbomify.com/CVE-2026-99108/index.md","name":"CVE-2026-99108","record":{"aliases":["DEBIAN-CVE-2026-99108","GHSA-8qcr-mmv6-jjc8","UBUNTU-CVE-2026-99108"],"analysis":null,"analysis_generated_by":null,"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\nntfs: fix FITRIM range alignment\n\nntfs_trim_fs() aligns the start of a free extent up to the device discard\ngranularity, but derives the discard length by aligning the original extent\nlength down. When the free extent start is not discard-aligned, adding that\nlength to the aligned start can extend the discard past the free extent and\ninto allocated clusters.\n\nFor example, with 4 KiB clusters and 32 KiB discard granularity, the free\nextent [4 KiB, 36 KiB) becomes the discard range [32 KiB, 64 KiB), so\n28 KiB beyond the free extent may be discarded.\n\nAlign the absolute end of the free extent down and derive the length from\nthe two aligned endpoints. Skip extents that contain no full discard unit.\n\nReproduced with a 4 KiB-cluster NTFS filesystem on scsi_debug configured\nfor 32 KiB discard granularity and read-zero-after-trim. Before this\nchange, FITRIM zeroed seven allocated 4 KiB clusters following an unaligned\n32 KiB hole. With this change, the same data remains intact across FITRIM\nand remount.","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":"ntfs: fix FITRIM range alignment","id":"CVE-2026-99108","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"smb: client: reject SetEA requests that do not fit the request buffer","id":"CVE-2026-99109"},"packages":[],"prev":{"headline":"ntfs: fix incorrect MFT record pointer passed to ntfs_attr_record_resize","id":"CVE-2026-99107"},"products":["Linux"],"published":"2026-10-28","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-28","vendors":["Linux"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-99108/"}