{ "schema_version": "1.6.1", "id": "RPI-CVE-2026-89523", "modified": "2026-10-09T11:39:44Z", "upstream": [ "CVE-2026-89523" ], "published": "2026-09-11T19:47:07Z", "summary": "wifi: mt76: mt7925: cancel pending mlo_pm_work", "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: mt76: mt7925: cancel pending mlo_pm_work\n\nIf the device is reset, suspended or unregistered within that window,\nthe pending work can still run and access vif/bss data that may already\nbe freed, or send MCU commands while the firmware is not available.\n\nAdd cancel_delayed_work_sync(&dev->mlo_pm_work) in all relevant teardown\nand suspend paths:\n\n - mt7925_mac_reset_work() (chip reset recovery)\n - mt7925e_unregister_device() (PCIe unbind)\n - mt7925_pci_suspend() (PCIe bus suspend)\n - mt7925_suspend() (mac80211 suspend)\n - mt7925u_suspend() (USB bus / runtime suspend)\n\nThis ensures the work is stopped before the device state becomes\ninvalid.", "severity": [ { "type": "CVSS_V3", "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H" } ], "affected": [ { "package": { "ecosystem": "Raspberry Pi OS:13", "name": "linux" }, "versions": [ "1:6.18.29-1+rpt1", "1:6.18.33-1+rpt1", "1:6.18.34-1+rpt1", "1:6.18.39-1+rpt1" ], "ecosystem_specific": { "binaries": [ { "binary_name": "linux-image-6.18.29+rpt-rpi-2712", "binary_version": "1:6.18.29-1+rpt1" }, { "binary_name": "linux-image-6.18.29+rpt-rpi-v6", "binary_version": "1:6.18.29-1+rpt1" }, { "binary_name": "linux-image-6.18.29+rpt-rpi-v7", "binary_version": "1:6.18.29-1+rpt1" }, { "binary_name": "linux-image-6.18.29+rpt-rpi-v8", "binary_version": "1:6.18.29-1+rpt1" }, { "binary_name": "linux-image-6.18.29+rpt-rpi-v8-rt", "binary_version": "1:6.18.29-1+rpt1" }, { "binary_name": "linux-image-6.18.33+rpt-rpi-2712", "binary_version": "1:6.18.33-1+rpt1" }, { "binary_name": "linux-image-6.18.33+rpt-rpi-v6", "binary_version": "1:6.18.33-1+rpt1" }, { "binary_name": "linux-image-6.18.33+rpt-rpi-v7", "binary_version": "1:6.18.33-1+rpt1" }, { "binary_name": "linux-image-6.18.33+rpt-rpi-v8", "binary_version": "1:6.18.33-1+rpt1" }, { "binary_name": "linux-image-6.18.33+rpt-rpi-v8-rt", "binary_version": "1:6.18.33-1+rpt1" }, { "binary_name": "linux-image-6.18.34+rpt-rpi-2712", "binary_version": "1:6.18.34-1+rpt1" }, { "binary_name": "linux-image-6.18.34+rpt-rpi-v6", "binary_version": "1:6.18.34-1+rpt1" }, { "binary_name": "linux-image-6.18.34+rpt-rpi-v7", "binary_version": "1:6.18.34-1+rpt1" }, { "binary_name": "linux-image-6.18.34+rpt-rpi-v8", "binary_version": "1:6.18.34-1+rpt1" }, { "binary_name": "linux-image-6.18.34+rpt-rpi-v8-rt", "binary_version": "1:6.18.34-1+rpt1" }, { "binary_name": "linux-image-6.18.39+rpt-rpi-2712", "binary_version": "1:6.18.39-1+rpt1" }, { "binary_name": "linux-image-6.18.39+rpt-rpi-v6", "binary_version": "1:6.18.39-1+rpt1" }, { "binary_name": "linux-image-6.18.39+rpt-rpi-v7", "binary_version": "1:6.18.39-1+rpt1" }, { "binary_name": "linux-image-6.18.39+rpt-rpi-v8", "binary_version": "1:6.18.39-1+rpt1" }, { "binary_name": "linux-image-6.18.39+rpt-rpi-v8-rt", "binary_version": "1:6.18.39-1+rpt1" } ] }, "database_specific": { "per_version": { "1:6.18.29-1+rpt1": { "linux_commit": "66318c5b5cd8145a662303af12ed39ac07eb27cc", "upstream_version": "6.18.29", "assessment": "commit ancestry (strak rule)", "upstream_fixed": "6.18.50" }, "1:6.18.33-1+rpt1": { "linux_commit": "95b85bebbedcaedfa7ca79116ed38b7376fba412", "upstream_version": "6.18.33", "assessment": "commit ancestry (strak rule)", "upstream_fixed": "6.18.50" }, "1:6.18.34-1+rpt1": { "linux_commit": "c8c7494100e99ee05b11aaa4f0588a223a63d1af", "upstream_version": "6.18.34", "assessment": "commit ancestry (strak rule)", "upstream_fixed": "6.18.50" }, "1:6.18.39-1+rpt1": { "linux_commit": "60ea684a8ace97bb0db1a16e20753bdd6ab371ff", "upstream_version": "6.18.39", "assessment": "commit ancestry (strak rule)", "upstream_fixed": "6.18.50" } } } } ], "references": [ { "type": "ADVISORY", "url": "https://www.cve.org/CVERecord?id=CVE-2026-89523" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/5be6d02837d418bc6c805b5cab1b338de6de9ca7" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/c5e073f2fbfd34d22099a50d96f60990799753e2" }, { "type": "FIX", "url": "https://git.kernel.org/stable/c/2889e84282dda147f10b10d94cf0efd90a349c53" } ], "database_specific": { "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git", "upstream_modified": "2026-09-13T06:49:25Z", "severity": { "source": "kernel CNA", "cvss_v3_score": 7.8, "cvss_v3_severity": "High", "scenario": "AV:L - The bug leaves mlo_pm_work armed across local mt7925 teardown: chip-reset recovery, PCI unbind, and PCIe/mac80211/USB suspend. Those are host driver-lifecycle and power-management paths; over-the-air frames do not invoke them, matching other mt76 cleanup UAFs.\nAC:L - mt7925 queues mlo_pm_work with a fixed 5-second delay during MLO power-save setup. A local attacker who associates to a Wi-Fi 7 MLO AP and then immediately suspends, unbinds, or resets the device controls both sides and easily hits that window, with no attacker-uncontrollable race or heap layout.\nPR:L - MLO association uses nl80211 connect (GENL_UNS_ADMIN_PERM/CAP_NET_ADMIN). Logged-in users can then suspend via logind/polkit or Android autosleep, and NetworkManager/Android Wi-Fi controls expose this without init-namespace root, so privileges are Low.\nUI:N - The attacker performs MLO association and the subsequent suspend, PCI/USB unbind, or reset themselves. No separate victim action such as opening a file or mounting a filesystem is required.\nS:U - The use-after-free is of host kernel vif/bss_conf objects and the mt792x_dev-embedded delayed_work inside the mt7925 driver. It does not cross a VM, IOMMU, or sandbox security boundary.\nC:H - PCI/USB unbind runs ieee80211_unregister_hw, which destroys the phy workqueue, then mt76_free_device() frees the mt792x_dev that embeds mlo_pm_work while the 5s timer still points at them. The worker also dereferences vif/bss_conf that remove_interface or change_vif_links may already have freed, enabling disclosure via heap reclaim.\nI:H - The dangling delayed_work timer can fire on a freed mt792x_dev after unbind, and mt7925_mlo_pm_iter can send MCU BSS_INFO_UPDATE through stale mconf/vif objects. That is a classic timer/workqueue UAF exploitable for writes and control-flow hijack, so Integrity is High.\nA:H - The pending worker can WARN in __queue_work on a destroying phy workqueue, NULL-dereference a removed MLO link_conf, or issue MCU commands while firmware is reset or suspended, causing a kernel oops or panic. Any such crash is Availability High." } } }