{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89832 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89832 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-89832 and fix it if it is affected.\n\nWhat it is: CVE-2026-89832 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-89832 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-89832/ (Markdown: https://insights.sbomify.com/CVE-2026-89832/index.md)","id":"CVE-2026-89832","markdown":"https://insights.sbomify.com/CVE-2026-89832/index.md","name":"CVE-2026-89832","record":{"aliases":["AZL-101258","BELL-CVE-2026-89832","DEBIAN-CVE-2026-89832","GHSA-wf2c-cvqr-xhr7","UBUNTU-CVE-2026-89832"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel filesystem","requires_auth":"low_privilege","summary":"A flaw in the Linux kernel f2fs filesystem fails to clear dirty flags on corrupted node folios, potentially leading to inconsistent data persistence.","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 clear dirty flag on folio in error path\n\nIf node block is corrupted due to chksum mismatch or inconsistent\nfooter info, it needs to drop clear flag of node folio, in order\nto persist inconsistent node data to storage.","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 clear dirty flag on folio in error path","id":"CVE-2026-89832","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"f2fs: fix to avoid potential deadloop in f2fs_fsync_node_pages()","id":"CVE-2026-89833"},"packages":[],"prev":{"headline":"f2fs: protect critical_task_priority updates with s_umount","id":"CVE-2026-89831"},"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-21","vendors":["Linux"]},"summary":"A flaw in the Linux kernel f2fs filesystem fails to clear dirty flags on corrupted node folios, potentially leading to inconsistent data persistence.","url":"https://insights.sbomify.com/CVE-2026-89832/"}