{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89600 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89600 is a high-severity use after free vulnerability in Linux, published on 11 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-89600 and fix it if it is affected.\n\nWhat it is: CVE-2026-89600 is a high-severity use after free vulnerability in Linux, published on 11 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-89600 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-89600/ (Markdown: https://insights.sbomify.com/CVE-2026-89600/index.md)","id":"CVE-2026-89600","markdown":"https://insights.sbomify.com/CVE-2026-89600/index.md","name":"CVE-2026-89600","record":{"aliases":["BELL-CVE-2026-89600","DEBIAN-CVE-2026-89600","GHSA-hfc9-63gq-6mcj","UBUNTU-CVE-2026-89600"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A use-after-free in the Linux kernel fanotify subsystem allows attackers to read stale stack data or cause a system crash.","user_interaction":"not_required","vuln_class":"use_after_free"},"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\nfanotify: fix use-after-free of file range info\n\nfsnotify_pre_content() builds its file_range on the triggering task's\nstack. fanotify_alloc_perm_event() saves a pointer to range.pos in the\nheap-allocated permission event so copy_range_info_to_user() can report\nthe offset later.\n\nThe event reader can set the event state to FAN_EVENT_REPORTED and then\nsleep while preparing the file descriptor. If a signal interrupts the\ntriggering task at that point, fanotify_get_response() changes the state\nto FAN_EVENT_CANCELED and returns. This unwinds the file_range stack\nframe while the reader still owns the event. The reader then dereferences\npevent-\u003eppos and copies the stale stack value to userspace.\n\nKASAN reported:\n\n  BUG: KASAN: use-after-free in fanotify_read+0x293e/0x2970\n  Read of size 8 at addr ffff88811434fc50 by task fanotify_inotif/95\n  Call Trace:\n   fanotify_read+0x293e/0x2970\n   vfs_read+0x177/0xa20\n   ksys_read+0xf7/0x1c0\n   do_syscall_64+0xf9/0x540\n   entry_SYSCALL_64_after_hwframe+0x77/0x7f\n\nStore the range position directly in the permission event and use\nFANOTIFY_NO_RANGE when range information is unavailable. The event remains\nalive until the reader finishes, so the reported offset no longer depends\non the triggering task's stack.","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":"fanotify: fix use-after-free of file range info","id":"CVE-2026-89600","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"ext2: Fix lost inode updates for IS_SYNC inodes","id":"CVE-2026-89601"},"packages":[],"prev":{"headline":"fbdev: omapfb: panel-dsi-cm: initialize lock before registering display","id":"CVE-2026-89599"},"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-19","vendors":["Linux"]},"summary":"A use-after-free in the Linux kernel fanotify subsystem allows attackers to read stale stack data or cause a system crash.","url":"https://insights.sbomify.com/CVE-2026-89600/"}