{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-97973 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-97973 is a memory corruption vulnerability in Linux, published on 25 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-97973 and fix it if it is affected.\n\nWhat it is: CVE-2026-97973 is a memory corruption vulnerability in Linux, published on 25 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-97973 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-97973/ (Markdown: https://insights.sbomify.com/CVE-2026-97973/index.md)","id":"CVE-2026-97973","markdown":"https://insights.sbomify.com/CVE-2026-97973/index.md","name":"CVE-2026-97973","record":{"aliases":["AZL-104835","BELL-CVE-2026-97973","DEBIAN-CVE-2026-97973","GHSA-rvwv-vg3x-5m3f","UBUNTU-CVE-2026-97973"],"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":"none","summary":"A memory leak in the Linux kernel macb driver probe error path can lead to resource 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\nnet: macb: destroy the phylink instance on the probe error path\n\nmacb_mii_init() creates a phylink instance on both of its success paths,\nbut the probe unwind frees the netdev without destroying it, so a failing\nmacb_alloc_tieoff() or register_netdev() leaks the instance.\n\nDestroy it at err_out_unregister_mdio, which is only reachable once\nmacb_mii_init() has succeeded, so bp-\u003ephylink is valid there.","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":"net: macb: destroy the phylink instance on the probe error path","id":"CVE-2026-97973","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"ipv6: null-check fib6_node before accessing in __ip6_del_rt_siblings()","id":"CVE-2026-97974"},"packages":[],"prev":{"headline":"net: macb: put the \"mdio\" child node reference on success","id":"CVE-2026-97972"},"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":"A memory leak in the Linux kernel macb driver probe error path can lead to resource exhaustion and denial of service.","url":"https://insights.sbomify.com/CVE-2026-97973/"}