{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89746 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89746 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-89746 and fix it if it is affected.\n\nWhat it is: CVE-2026-89746 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-89746 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-89746/ (Markdown: https://insights.sbomify.com/CVE-2026-89746/index.md)","id":"CVE-2026-89746","markdown":"https://insights.sbomify.com/CVE-2026-89746/index.md","name":"CVE-2026-89746","record":{"aliases":["AZL-100169","BELL-CVE-2026-89746","DEBIAN-CVE-2026-89746","GHSA-m56h-pfxh-qxq7","UBUNTU-CVE-2026-89746"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel tracing","requires_auth":"low_privilege","summary":"A use-after-free in Linux kernel tracing allows local attackers to cause a kernel panic or potentially execute code via crafted hist triggers.","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\ntracing: Fix use-after-free with same-name named triggers\n\nWhen two hist triggers on different events are registered with the same\nname=, the second one reuses the first as named_data.  Both are added to\ntr-\u003ehist_vars by save_hist_vars() during event_hist_trigger_parse(),\nbecause save_hist_vars() is called before event_trigger_register() while\nthe named reuse is only detected later, in hist_register_trigger().\n\nIn the named-data branch hist_register_trigger() then frees the second\nhistogram's hist_data via destroy_hist_data(), but never removes its\ntr-\u003ehist_vars list entry, leaving a dangling pointer and leaking the\ntrace_array reference it holds.\n\nA later hist trigger that references a variable makes find_var_file()\nwalk tr-\u003ehist_vars and dereference the freed hist_data.  The bug is\nreproducible from userspace by writing three hist triggers to tracefs:\n\n  cd /sys/kernel/tracing\n  echo 'hist:keys=common_pid:x=common_pid:name=mh' \u003e events/sched/sched_switch/trigger\n  echo 'hist:keys=common_pid:x=common_pid:name=mh' \u003e events/sched/sched_process_fork/trigger\n  echo 'hist:keys=common_pid:vals=$x' \u003e events/sched/sched_process_exit/trigger\n\nThe third write panics the kernel:\n\n  BUG: KASAN: slab-use-after-free in find_var_file.part.0+0x272/0x290\n  Read of size 8 at addr ffff888001f8a0e0 by task sh/1\n  CPU: 1 UID: 0 PID: 1 Comm: sh Tainted: G      D          N\n  Call Trace:\n    find_var_file.part.0\n    find_event_var\n    parse_atom\n    parse_expr\n    __create_val_field\n    event_hist_trigger_parse\n    trigger_process_regex\n    event_trigger_write\n    vfs_write\n    ksys_write\n    do_syscall_64\n    entry_SYSCALL_64_after_hwframe\n  Allocated by task 1:\n    event_hist_trigger_parse\n  Freed by task 1:\n    hist_register_trigger+0x618/0xa30\n    event_hist_trigger_parse\n  The buggy address belongs to freed 2048-byte region\n  Oops: general protection fault ... RIP: find_var_file.part.0\n  Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b\n\nFix by removing the hist_data from tr-\u003ehist_vars and releasing the\ntrace_array reference in the named-data branch of hist_register_trigger()\nbefore freeing the hist_data.","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":"tracing: Fix use-after-free with same-name named triggers","id":"CVE-2026-89746","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"tracing: Fix use-after-free in trace_pipe read on sub-buffer order change","id":"CVE-2026-89747"},"packages":[],"prev":{"headline":"debugfs: Fix lockdown check for mmap_prepare","id":"CVE-2026-89745"},"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 Linux kernel tracing allows local attackers to cause a kernel panic or potentially execute code via crafted hist triggers.","url":"https://insights.sbomify.com/CVE-2026-89746/"}