{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89829 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89829 is a high-severity vulnerability in Linux, published on 16 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-89829 and fix it if it is affected.\n\nWhat it is: CVE-2026-89829 is a high-severity vulnerability in Linux, published on 16 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-89829 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-89829/ (Markdown: https://insights.sbomify.com/CVE-2026-89829/index.md)","id":"CVE-2026-89829","markdown":"https://insights.sbomify.com/CVE-2026-89829/index.md","name":"CVE-2026-89829","record":{"aliases":["BELL-CVE-2026-89829","DEBIAN-CVE-2026-89829","GHSA-4f5r-rjrj-j99g","UBUNTU-CVE-2026-89829"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["other"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A logic error in the f2fs filesystem caused incorrect node ID validation, potentially leading to undefined behavior or stability issues.","user_interaction":"not_required","vuln_class":"other"},"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:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nf2fs: fix to pass folio-\u003eindex to f2fs_sanity_check_node_footer()\n\nOtherwise in f2fs_sanity_check_node_footer(), it will check the\nsame nid incorrectly.","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":"f2fs: fix to pass folio-\u003eindex to f2fs_sanity_check_node_footer()","id":"CVE-2026-89829","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"f2fs: fix valid block count leak on data block allocation failure","id":"CVE-2026-89830"},"packages":[],"prev":{"headline":"drm/amdgpu: Fix init ordering in amdgpu_vram_mgr_init()","id":"CVE-2026-89828"},"products":["Linux"],"published":"2026-09-16","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 logic error in the f2fs filesystem caused incorrect node ID validation, potentially leading to undefined behavior or stability issues.","url":"https://insights.sbomify.com/CVE-2026-89829/"}