{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-74325 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-74325 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-74325 and fix it if it is affected.\n\nWhat it is: CVE-2026-74325 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-74325 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-74325/ (Markdown: https://insights.sbomify.com/CVE-2026-74325/index.md)","id":"CVE-2026-74325","markdown":"https://insights.sbomify.com/CVE-2026-74325/index.md","name":"CVE-2026-74325","record":{"aliases":["BELL-CVE-2026-74325","DEBIAN-CVE-2026-74325","GHSA-4hx5-9m7x-6xgv","UBUNTU-CVE-2026-74325"],"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 WiFi driver","requires_auth":"low_privilege","summary":"A use-after-free vulnerability in the Linux kernel mt76 WiFi driver allows attackers to cause denial of service or execute code via improper memory handling.","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\nwifi: mt76: use kfree_rcu for offchannel link in mt76_put_vif_phy_link\n\nmt76_put_vif_phy_link() frees the offchannel mlink with plain kfree()\nafter rcu_assign_pointer(NULL). However, rcu_assign_pointer only prevents\nfuture RCU readers from obtaining the pointer -- it does not wait for\nexisting readers that already hold it via rcu_dereference.\n\nThe TX datapath (e.g. mt7996_mac_write_txwi) dereferences mlink-\u003ewcid\nand mlink-\u003eidx under rcu_read_lock. If a TX softirq obtained the pointer\nvia rcu_dereference just before the NULL assignment, it will dereference\nfreed memory after the kfree.\n\nstruct mt76_vif_link already contains an rcu_head field that is unused at\nthis free site -- a developer oversight, since the adjacent\nkfree_rcu_mightsleep call for rx_sc in the same function shows the\npattern was understood.\n\nReplace kfree(mlink) with kfree_rcu(mlink, rcu_head).","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":"wifi: mt76: use kfree_rcu for offchannel link in mt76_put_vif_phy_link","id":"CVE-2026-74325","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"wifi: mt76: mt7921: fix resource leak in probe error path","id":"CVE-2026-74326"},"packages":[],"prev":{"headline":"wifi: mt76: mt7925: validate skb length in testmode query","id":"CVE-2026-74324"},"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 use-after-free vulnerability in the Linux kernel mt76 WiFi driver allows attackers to cause denial of service or execute code via improper memory handling.","url":"https://insights.sbomify.com/CVE-2026-74325/"}