{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72307 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72307 is a memory corruption 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-72307 and fix it if it is affected.\n\nWhat it is: CVE-2026-72307 is a memory corruption 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-72307 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-72307/ (Markdown: https://insights.sbomify.com/CVE-2026-72307/index.md)","id":"CVE-2026-72307","markdown":"https://insights.sbomify.com/CVE-2026-72307/index.md","name":"CVE-2026-72307","record":{"aliases":["BELL-CVE-2026-72307","DEBIAN-CVE-2026-72307","GHSA-7fcx-hvpg-5c9p","UBUNTU-CVE-2026-72307"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"high_privilege","summary":"A refcount leak in the mlxsw driver allows local attackers to cause memory exhaustion and denial of service.","user_interaction":"not_required","vuln_class":"memory_corruption"},"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\nmlxsw: fix refcount leak in mlxsw_sp_vrs_lpm_tree_replace()\n\nWhen mlxsw_sp_vrs_lpm_tree_replace() fails after replacing some VRs,\nthe error rollback loop does not correctly revert the preceding\nreplacements. The loop decrements the index but fails to update the\nvr pointer, which still points to the VR that caused the failure. As\na result, the condition and the rollback call always operate on the\nsame VR, potentially calling mlxsw_sp_vr_lpm_tree_replace() multiple\ntimes on it while never rolling back the earlier VRs. Those VRs\ncontinue to hold a reference to new_tree acquired via\nmlxsw_sp_lpm_tree_hold(), leaking the reference count of new_tree.\n\nFix by reinitializing vr inside the error loop with the updated index:\n\n\tvr = \u0026mlxsw_sp-\u003erouter-\u003evrs[i];\n\nso that the loop correctly iterates over all VRs that were actually\nreplaced.","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":"mlxsw: fix refcount leak in mlxsw_sp_vrs_lpm_tree_replace()","id":"CVE-2026-72307","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"mlxsw: fix refcount leak in mlxsw_sp_port_lag_join()","id":"CVE-2026-72308"},"packages":[],"prev":{"headline":"vduse: Fix race in vduse_dev_msg_sync and vduse_dev_read_iter","id":"CVE-2026-72306"},"products":["Linux"],"published":"2026-08-15","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-08-17","vendors":["Linux"]},"summary":"A refcount leak in the mlxsw driver allows local attackers to cause memory exhaustion and denial of service.","url":"https://insights.sbomify.com/CVE-2026-72307/"}