{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89486 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89486 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-89486 and fix it if it is affected.\n\nWhat it is: CVE-2026-89486 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-89486 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-89486/ (Markdown: https://insights.sbomify.com/CVE-2026-89486/index.md)","id":"CVE-2026-89486","markdown":"https://insights.sbomify.com/CVE-2026-89486/index.md","name":"CVE-2026-89486","record":{"aliases":["BELL-CVE-2026-89486","DEBIAN-CVE-2026-89486","GHSA-6jq9-cvjw-v2h5","UBUNTU-CVE-2026-89486"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel IPMI","requires_auth":"low_privilege","summary":"A use-after-free in the Linux kernel IPMI driver allows attackers to potentially execute code or escalate privileges due to missing RCU synchronization.","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\nipmi: Fix use-after-free of cmd_rcvr in _ipmi_destroy_user()\n\nCommit 9e91f8a6c868 (\"ipmi:msghandler: Remove srcu for the\nipmi_interfaces list\") dropped the synchronize_rcu() between unlinking\nthe command receivers from intf-\u003ecmd_rcvrs and freeing them, updating\nonly the comment that explains why the barrier is needed.\n\nThe cmd_rcvrs list is still traversed under plain RCU: find_cmd_rcvr()\nwalks it inside rcu_read_lock(), and handle_ipmb_get_msg_cmd() borrows\nrcvr-\u003euser from that lookup within the same read-side section. Without\nthe grace period, _ipmi_destroy_user() can kfree() a cmd_rcvr while a\nreader still holds a pointer to it, causing a use-after-free.\n\nThe rework only made srcu unnecessary for the interfaces list; the\ncmd_rcvrs list still relies on plain RCU. Restore the synchronize_rcu()\nbefore freeing the receivers.","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":"ipmi: Fix use-after-free of cmd_rcvr in _ipmi_destroy_user()","id":"CVE-2026-89486","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":"openvswitch: only skb_tx_error() a packet we are about to drop","id":"CVE-2026-89487"},"packages":[],"prev":{"headline":"lockd: pin next file across nlm_inspect_file lock-drop","id":"CVE-2026-89485"},"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 IPMI driver allows attackers to potentially execute code or escalate privileges due to missing RCU synchronization.","url":"https://insights.sbomify.com/CVE-2026-89486/"}