{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-99098 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-99098 is a vulnerability in Linux, published on 26 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-99098 and fix it if it is affected.\n\nWhat it is: CVE-2026-99098 is a vulnerability in Linux, published on 26 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-99098 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-99098/ (Markdown: https://insights.sbomify.com/CVE-2026-99098/index.md)","id":"CVE-2026-99098","markdown":"https://insights.sbomify.com/CVE-2026-99098/index.md","name":"CVE-2026-99098","record":{"aliases":["BELL-CVE-2026-99098","DEBIAN-CVE-2026-99098","GHSA-wfqx-5v3g-mpcg","UBUNTU-CVE-2026-99098"],"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\ndm-integrity: fix buffer overflow in inline mode with large tag size\n\nIn inline mode, dm_integrity_check and dm_integrity_inline_recheck\ncompute the checksum of each block into an on-stack buffer of\nHASH_MAX_DIGESTSIZE bytes. integrity_sector_checksum pads its result\nwith zeroes up to the tag size, so if the tag size is larger than\nHASH_MAX_DIGESTSIZE, the padding runs past the end of the buffer. With\nCONFIG_STACKPROTECTOR the kernel panics in dm_integrity_check on the\nfirst read.\n\nEnlarge both buffers to hold MAX_TAG_SIZE bytes, as commit b93b6643e9b5\n(\"dm integrity: fix a crash with unusually large tag size\") did for\nintegrity_metadata.\n\nNote that this is not a security bug because the buffer overflow can only\nbe triggered by root.","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":"dm-integrity: fix buffer overflow in inline mode with large tag size","id":"CVE-2026-99098","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"x86/CPU/AMD: Fix AMD TLBI Erratum #1718","id":"CVE-2026-99099"},"packages":[],"prev":{"headline":"tee: shm: reject zero-sized allocations in tee_dyn_shm_alloc_helper()","id":"CVE-2026-99097"},"products":["Linux"],"published":"2026-10-26","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-26","vendors":["Linux"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-99098/"}