{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-97443 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-97443 is a denial of service vulnerability in Linux, published on 24 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-97443 and fix it if it is affected.\n\nWhat it is: CVE-2026-97443 is a denial of service vulnerability in Linux, published on 24 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-97443 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-97443/ (Markdown: https://insights.sbomify.com/CVE-2026-97443/index.md)","id":"CVE-2026-97443","markdown":"https://insights.sbomify.com/CVE-2026-97443/index.md","name":"CVE-2026-97443","record":{"aliases":["AZL-103967","BELL-CVE-2026-97443","DEBIAN-CVE-2026-97443","GHSA-c83f-fgh5-9532","UBUNTU-CVE-2026-97443"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A local attacker can trigger a kernel warning and potential instability by exploiting improper ftrace function unregistration during error cleanup paths.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nperf/ftrace: Fix WARNING in __unregister_ftrace_function\n\nperf_ftrace_function_unregister() unconditionally calls\nunregister_ftrace_function() without checking whether the ftrace_ops\nwas ever successfully registered. This triggers a WARN_ON in\n__unregister_ftrace_function() when the ops doesn't have\nFTRACE_OPS_FL_ENABLED set.\n\nThis can happen during perf_event_alloc() error cleanup when\nperf_trace_destroy() is called via __free_event() on an event whose\nftrace_ops registration failed or was already torn down by\nperf_try_init_event()'s err_destroy path.\n\nThe call path is:\n  perf_event_alloc() error cleanup\n    -\u003e __free_event()\n      -\u003e event-\u003edestroy() [tp_perf_event_destroy]\n        -\u003e perf_trace_destroy()\n          -\u003e perf_trace_event_close()\n            -\u003e TRACE_REG_PERF_CLOSE\n              -\u003e perf_ftrace_function_unregister()\n                -\u003e unregister_ftrace_function()\n                  -\u003e __unregister_ftrace_function()\n                    -\u003e WARN_ON(!(ops-\u003eflags \u0026 FTRACE_OPS_FL_ENABLED))\n\nFix this by checking FTRACE_OPS_FL_ENABLED before attempting to\nunregister. If the ops is not enabled, just free the filter and\nreturn success.","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":"perf/ftrace: Fix WARNING in __unregister_ftrace_function","id":"CVE-2026-97443","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"ACPICA: add boundary checks in two places","id":"CVE-2026-97444"},"packages":[],"prev":{"headline":"wifi: ath11k: fix invalid data access in ath11k_dp_rx_h_undecap_nwifi","id":"CVE-2026-97442"},"products":["Linux"],"published":"2026-09-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-09-25","vendors":["Linux"]},"summary":"A local attacker can trigger a kernel warning and potential instability by exploiting improper ftrace function unregistration during error cleanup paths.","url":"https://insights.sbomify.com/CVE-2026-97443/"}