From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 221EF54CF6D for ; Fri, 11 Sep 2026 19:45:59 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1789155976; cv=none; b=Jog9/83Ok9KHMruLLq/JLLIM9YFc02nXMZ7Kds5wuiNVxL3b5qR1DUmbD4zxDlREJQLNgYjsR/wnvg/FnHUn87LrEWG3mpjVOYecse89L3mqNK2vpAXin5sdBqhZizhGH4Fj0ILvrhcJB2ACYaMJHNJh/lbZC0sgvVoiPJCQV4c= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1789155976; c=relaxed/simple; bh=U11XQOvFG4wU53eTQL6SNoRHhFO8/WYxAdOv3flMNts=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=G1/3J9AGNfcCK75zNdNIxoH2sgdWozOoxWu74XdSVpD5+RWhONozU0Q1DeykwKVGKlnQTaW+W/Gl5dW4KCv1aKouZCPjSMWiwXhaGyA/gxsQ8EG8X/fkhHIO9jM7yl16MHuhxQNnHjKYX0SZporaroV1YoMqE8Y3yO7vv0UDE4I= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=WQf4FW1n; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="WQf4FW1n" Received: by smtp.kernel.org (Postfix) with ESMTPSA id EE3861F00899; Fri, 11 Sep 2026 19:45:55 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1789155956; bh=yAHgUt/vDlruMPYzWp+os0kcsW1vUyJSq9gx+P29GZA=; h=From:To:Cc:Subject:Date:Reply-To; b=WQf4FW1nqtv0cZK8jl8BqPoa/kRnNnY19W7PYlt4/FiNTKO76uEm7JaFc0M4peeLU YE8jxIXacWx6mD52ZXbpMnnDagG06ODkhlc5fm0Yy+oR4Qass3q0nNSjOoMD96JlLl TkQSZ8IK9Lhx7h4vU+QWrLZ3Bz2NrRj4zD9Olos4= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-80939: wifi: rtw89: pci: add .shutdown callback to stop rfkill polling on reboot Date: Fri, 11 Sep 2026 21:40:45 +0200 Message-ID: <2026091137-CVE-2026-80939-e612@gregkh> X-Mailer: git-send-email 2.55.0 Reply-To: , Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=3774; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=CQbmyRb+CmSH+hcp+/D5nCRQCTQkvfwIygsusiHHDdM=; b=owGbwMvMwCRo6H6F97bub03G02pJDFlLIk2ZfD69b24pyd9w2X2p8OvDh/S3+Mdl8ouaxtYIN rCUOll3xLIwCDIxyIopsnzZxnN0f8UhRS9D29Mwc1iZQIYwcHEKwESS7RjmKXE/M1Scull+6h6O kjcsF/lutz+pYlgwsTeVR2NxL0P1u6rvm8/Ov/Hzw5u5AA== X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit From: Greg Kroah-Hartman Description =========== In the Linux kernel, the following vulnerability has been resolved: wifi: rtw89: pci: add .shutdown callback to stop rfkill polling on reboot Since the hardware rfkill polling was introduced, arm64 platforms can panic with an asynchronous SError during warm reboot: SError Interrupt on CPU8, code 0x00000000be000011 -- SError Workqueue: events_power_efficient rfkill_poll [rfkill] rtw89_pci_ops_read8+0x94/0x160 [rtw89_pci] rtw89_core_rfkill_poll+0x50/0x1e0 [rtw89_core] rtw89_ops_rfkill_poll+0x40/0x68 [rtw89_core] ieee80211_rfkill_poll+0x3c/0x70 [mac80211] cfg80211_rfkill_poll+0x40/0x2a0 [cfg80211] rfkill_poll+0x30/0x88 [rfkill] Kernel panic - not syncing: Asynchronous SError Interrupt On the reboot path the kernel only runs device_shutdown(), which calls each driver's .shutdown callback; .remove is not invoked. The rtw89 PCI driver had no .shutdown callback, so nothing stopped the rfkill polling work while the platform was tearing the PCIe link down. Once the link is gone, the next MMIO read from the poll handler targets a non-responding device and is reported as a fatal asynchronous SError on arm64. Add rtw89_pci_shutdown(), wired to all rtw89 PCI device drivers, which sets a new RTW89_FLAG_SHUTDOWN flag (mirroring the USB RTW89_FLAG_UNPLUGGED pattern). When the flag is set, rtw89_ops_rfkill_poll() returns early, so no MMIO read is issued to the chip after shutdown begins and the SError no longer occurs. This does not call the full .remove path from .shutdown, to keep the shutdown handler minimal and avoid running the non-idempotent teardown twice. The Linux kernel CVE team has assigned CVE-2026-80939 to this issue. Affected and fixed versions =========================== Issue introduced in 6.12 with commit 0b38e6277aed8a59ccb64fcc1172d962c1f11b4c and fixed in 7.2.4 with commit c1f214dd1351244156deb57761b14190a233aef6 Issue introduced in 6.12 with commit 0b38e6277aed8a59ccb64fcc1172d962c1f11b4c and fixed in 7.3-rc1 with commit 667c12782aaf8dd3cb2213e528fe63a73cb63345 Please see https://www.kernel.org for a full list of currently supported kernel versions by the kernel community. Unaffected versions might change over time as fixes are backported to older supported kernel versions. The official CVE entry at https://cve.org/CVERecord/?id=CVE-2026-80939 will be updated if fixes are backported, please check that for the most up to date information about this issue. Affected files ============== The file(s) affected by this issue are: drivers/net/wireless/realtek/rtw89/core.h drivers/net/wireless/realtek/rtw89/mac80211.c drivers/net/wireless/realtek/rtw89/pci.c drivers/net/wireless/realtek/rtw89/pci.h drivers/net/wireless/realtek/rtw89/rtw8851be.c drivers/net/wireless/realtek/rtw89/rtw8852ae.c drivers/net/wireless/realtek/rtw89/rtw8852be.c drivers/net/wireless/realtek/rtw89/rtw8852bte.c drivers/net/wireless/realtek/rtw89/rtw8852ce.c drivers/net/wireless/realtek/rtw89/rtw8922ae.c drivers/net/wireless/realtek/rtw89/rtw8922de.c Mitigation ========== The Linux kernel CVE team recommends that you update to the latest stable kernel version for this, and many other bugfixes. Individual changes are never tested alone, but rather are part of a larger kernel release. Cherry-picking individual commits is not recommended or supported by the Linux kernel community at all. If however, updating to the latest release is impossible, the individual changes to resolve this issue can be found at these commits: https://git.kernel.org/stable/c/c1f214dd1351244156deb57761b14190a233aef6 https://git.kernel.org/stable/c/667c12782aaf8dd3cb2213e528fe63a73cb63345