{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72120 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72120 is a high-severity 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-72120 and fix it if it is affected.\n\nWhat it is: CVE-2026-72120 is a high-severity 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-72120 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-72120/ (Markdown: https://insights.sbomify.com/CVE-2026-72120/index.md)","id":"CVE-2026-72120","markdown":"https://insights.sbomify.com/CVE-2026-72120/index.md","name":"CVE-2026-72120","record":{"aliases":["BELL-CVE-2026-72120","DEBIAN-CVE-2026-72120","GHSA-v4mr-5hv5-p6wp","UBUNTU-CVE-2026-72120"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel CAN BCM","requires_auth":"low_privilege","summary":"A race condition in the Linux kernel CAN BCM module due to missing RCU list operations can lead to system instability or crashes.","user_interaction":"not_required","vuln_class":"race_condition"},"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: bcm: add missing rcu list annotations and operations\n\nsashiko-bot remarked the missing use of list_add_rcu() in\nbcm_[rx|tx]_setup() to have a proper initialized bcm_op structure\nwhen bcm_proc_show() traverses the bcm_op's under rcu_read_lock().\n\nTo cover all initial settings of the bcm_op's the list_add_rcu() calls\nare moved to the end of the setup code.\n\nWhile at it, also fix the mirroring removal side: bcm_release() called\nbcm_remove_op() - which frees the op via call_rcu() - on ops that were\nstill linked in bo-\u003etx_ops/bo-\u003erx_ops, without list_del_rcu() first.\nUnlink each op with list_del_rcu() before handing it to bcm_remove_op(),\nmatching the existing pattern in bcm_delete_tx_op()/bcm_delete_rx_op().","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: bcm: add missing rcu list annotations and operations","id":"CVE-2026-72120","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"can: bcm: add locking when updating filter and timer values","id":"CVE-2026-72121"},"packages":[],"prev":{"headline":"can: bcm: extend bcm_tx_lock usage for data and timer updates","id":"CVE-2026-72119"},"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 BCM module due to missing RCU list operations can lead to system instability or crashes.","url":"https://insights.sbomify.com/CVE-2026-72120/"}