{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98931 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-98931 is a vulnerability in Linux, published on 23 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-98931 and fix it if it is affected.\n\nWhat it is: CVE-2026-98931 is a vulnerability in Linux, published on 23 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-98931 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-98931/ (Markdown: https://insights.sbomify.com/CVE-2026-98931/index.md)","id":"CVE-2026-98931","markdown":"https://insights.sbomify.com/CVE-2026-98931/index.md","name":"CVE-2026-98931","record":{"aliases":["AZL-110714","BELL-CVE-2026-98931","DEBIAN-CVE-2026-98931","GHSA-h8g8-r2jh-pj86","UBUNTU-CVE-2026-98931"],"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\nmtd: spinand: fix NULL pointer dereference with no ECC engine\n\nWhen \"nand-no-ecc-engine\" is set in DT, nanddev_get_ecc_engine() takes\nthe NAND_ECC_ENGINE_TYPE_NONE path and returns success while leaving\nnand-\u003eecc.engine NULL. The SPI-NAND code nevertheless dereferences it\nunconditionally to test for a pipelined engine, so probing such a\ndevice oopses immediately.\n\nRather than open-coding the test three times, add a\nnand_ecc_is_pipelined() helper to the NAND core that folds the NULL\ncheck into the integration comparison, and use it everywhere. Future\ncallers then cannot reintroduce the problem.","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":"mtd: spinand: fix NULL pointer dereference with no ECC engine","id":"CVE-2026-98931","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"EDAC/altera: Fix use-after-free in error paths","id":"CVE-2026-98932"},"packages":[],"prev":{"headline":"KVM: s390: Fix IRQ injection with SIGP Stop and Store Status","id":"CVE-2026-98930"},"products":["Linux"],"published":"2026-10-23","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-23","vendors":["Linux"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-98931/"}