{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72126 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72126 is a high-severity use after free vulnerability in Linux, published on 15 Aug 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-72126 and fix it if it is affected.\n\nWhat it is: CVE-2026-72126 is a high-severity use after free vulnerability in Linux, published on 15 Aug 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-72126 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-72126/ (Markdown: https://insights.sbomify.com/CVE-2026-72126/index.md)","id":"CVE-2026-72126","markdown":"https://insights.sbomify.com/CVE-2026-72126/index.md","name":"CVE-2026-72126","record":{"aliases":["BELL-CVE-2026-72126","DEBIAN-CVE-2026-72126","GHSA-5j9g-r9x8-9248","UBUNTU-CVE-2026-72126"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel CAN","requires_auth":"low_privilege","summary":"A race condition in the Linux kernel CAN ISO-TP module allows a use-after-free of a timer callback, potentially leading to code execution or 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\ncan: isotp: use unconditional synchronize_rcu() in isotp_release()\n\nisotp_notify() unregisters the (RCU) CAN filters via can_rx_unregister()\nand clears so-\u003ebound without waiting for a grace period. isotp_release()\nuses so-\u003ebound to decide whether it needs to call synchronize_rcu()\nbefore cancelling so-\u003erxtimer, so when NETDEV_UNREGISTER runs first it\nskips that synchronize_rcu() and can cancel the timer while an\nin-flight isotp_rcv() is still executing and about to re-arm it via\nisotp_send_fc(), leading to a use-after-free timer callback on the\nfreed socket.\n\nsakisho-bot remarked a problem with rtnl_lock held in isotp_notify(),\ntherefore make isotp_release() always call synchronize_rcu() before\ncancelling the timers, regardless of so-\u003ebound. This still closes the\noriginal race (isotp_notify() clearing so-\u003ebound without waiting for\nin-flight isotp_rcv() callers before isotp_release() cancels the RX\ntimer) without adding any RCU wait to the netdevice notifier path.","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":"can: isotp: use unconditional synchronize_rcu() in isotp_release()","id":"CVE-2026-72126","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"netdev-genl: report NAPI thread PID in the caller's pid namespace","id":"CVE-2026-72127"},"packages":[],"prev":{"headline":"can: isotp: fix use-after-free race with concurrent NETDEV_UNREGISTER","id":"CVE-2026-72125"},"products":["Linux"],"published":"2026-08-15","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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-16","vendors":["Linux"]},"summary":"A race condition in the Linux kernel CAN ISO-TP module allows a use-after-free of a timer callback, potentially leading to code execution or system crash.","url":"https://insights.sbomify.com/CVE-2026-72126/"}