{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89601 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89601 is a high-severity vulnerability in Linux, published on 11 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-89601 and fix it if it is affected.\n\nWhat it is: CVE-2026-89601 is a high-severity vulnerability in Linux, published on 11 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-89601 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-89601/ (Markdown: https://insights.sbomify.com/CVE-2026-89601/index.md)","id":"CVE-2026-89601","markdown":"https://insights.sbomify.com/CVE-2026-89601/index.md","name":"CVE-2026-89601","record":{"aliases":["AZL-100446","BELL-CVE-2026-89601","DEBIAN-CVE-2026-89601","GHSA-g65m-jqm9-5xv8","UBUNTU-CVE-2026-89601"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Linux kernel ext2","requires_auth":"low_privilege","summary":"A logic error in the Linux kernel ext2 filesystem causes lost inode updates for synchronous inodes, potentially leading to data inconsistency.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/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\next2: Fix lost inode updates for IS_SYNC inodes\n\next2_setsize() and ext2_xattr_set2() had a construct like:\n\n\tif (IS_SYNC(inode)) {\n\t\tsync_inode_metadata(inode, 1);\n\t} else {\n\t\tmark_inode_dirty(inode);\n\t}\n\nwhich leads to lost inode updates for IS_SYNC inodes because\nsync_inode_metadata() does anything only if the inode is already dirty\nand hence inode updates may be simply lost. Fix the problem by\nunconditionally marking the inode dirty and *then* call\nsync_inode_metadata().","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":"ext2: Fix lost inode updates for IS_SYNC inodes","id":"CVE-2026-89601","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"erofs: skip sufficiently large global buffers when resizing","id":"CVE-2026-89602"},"packages":[],"prev":{"headline":"fanotify: fix use-after-free of file range info","id":"CVE-2026-89600"},"products":["Linux"],"published":"2026-09-11","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 logic error in the Linux kernel ext2 filesystem causes lost inode updates for synchronous inodes, potentially leading to data inconsistency.","url":"https://insights.sbomify.com/CVE-2026-89601/"}