Skip to content
Threat Brief

← All advisories

CVE-2026-80939

Severity unknownNo known exploitationFix available

wifi: rtw89: pci: add .shutdown callback to stop rfkill polling on reboot

Record last updated

CVSS score

None

No score published yet

EPSS, chance of exploitation in 30 days

0.2%

Higher than 6% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

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.

Patching and mitigation

Patch status
Fix available (source: Microsoft MSRC)
Fix documented (source date)
Mitigation
None documented
Vendor guidance
msrc.microsoft.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom 0b38e6277aed8a59ccb64fcc1172d962c1f11b4c before dfe2b5b2056918d186ad890079a9e7ec1898429adfe2b5b2056918d186ad890079a9e7ec1898429aCVE Program
LinuxLinuxfrom 0b38e6277aed8a59ccb64fcc1172d962c1f11b4c before 9693980cd7d2f5b17e5ef5922b922f2e1a770fca9693980cd7d2f5b17e5ef5922b922f2e1a770fcaCVE Program
LinuxLinuxfrom 0b38e6277aed8a59ccb64fcc1172d962c1f11b4c before c1f214dd1351244156deb57761b14190a233aef6c1f214dd1351244156deb57761b14190a233aef6CVE Program
LinuxLinuxfrom 0b38e6277aed8a59ccb64fcc1172d962c1f11b4c before 667c12782aaf8dd3cb2213e528fe63a73cb63345667c12782aaf8dd3cb2213e528fe63a73cb63345CVE Program
LinuxLinux6.12Not documentedCVE Program
Microsoftazl4 kernel 6.18.50-1.5.azl4 on Azure Linux 4.0Not documented0:6.18.57-1.1.azl4Microsoft MSRC
LinuxLinux (unaffected)from 6.12.112 up to and including 6.12.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.18.52 up to and including 6.18.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.2.4 up to and including 7.2.*Not documentedCVE Program
LinuxLinux (unaffected)7.3Not documentedCVE Program
LinuxLinux (unaffected)all versions before 6.12Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Advisory

    Microsoft advisory published

    Source: Microsoft MSRC (opens in a new tab)

  3. Patch

    Fix documented by Microsoft MSRC

    Source: Microsoft MSRC (opens in a new tab)

Vendor guidance and references