{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-97599 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-97599 is a vulnerability in Linux, published on 25 Sep 2026."},"fix_prompt":"Check this codebase for CVE-2026-97599 and fix it if it is affected.\n\nWhat it is: CVE-2026-97599 is a vulnerability in Linux, published on 25 Sep 2026. \nExploitation: There is no known exploitation of CVE-2026-97599 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-97599/ (Markdown: https://insights.sbomify.com/CVE-2026-97599/index.md)","id":"CVE-2026-97599","markdown":"https://insights.sbomify.com/CVE-2026-97599/index.md","name":"CVE-2026-97599","record":{"aliases":["AZL-104658","BELL-CVE-2026-97599","DEBIAN-CVE-2026-97599","GHSA-r8g8-vw6g-m8xh","UBUNTU-CVE-2026-97599"],"analysis":null,"analysis_generated_by":null,"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\nieee802154: hwsim: serialize pib updates to fix double-free\n\nhwsim_update_pib() does an unserialized read-swap-free of phy-\u003epib:\n\n\tpib_old = rtnl_dereference(phy-\u003epib);\n\t...\n\trcu_assign_pointer(phy-\u003epib, pib);\n\tkfree_rcu(pib_old, rcu);\n\nIt assumes the RTNL is held, but -\u003eset_channel is not always called\nunder it: the mac802154 scan worker changes channels via\ndrv_set_channel() without the RTNL. Such an update can race an\nRTNL-held one on the same phy; both read the same pib_old and both\nkfree_rcu() it, double-freeing the object. With SLUB percpu sheaves\nbatching kfree_rcu(), this surfaces as a KASAN invalid-free in\nrcu_free_sheaf().\n\nstruct hwsim_phy has no lock for pib. Add one and make the swap atomic\nwith rcu_replace_pointer() under it, dropping the misleading\nrtnl_dereference().","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":"ieee802154: hwsim: serialize pib updates to fix double-free","id":"CVE-2026-97599","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"ieee802154: cc2520: fix FIFOP work use-after-free","id":"CVE-2026-97600"},"packages":[],"prev":{"headline":"ipv4: fib: bound automatic table ID allocation","id":"CVE-2026-97598"},"products":["Linux"],"published":"2026-09-25","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-10-19","vendors":["Linux"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-97599/"}