CVE-2026-46092

wifi: rtw88: check for PCI upstream bridge existence

MEDIUM

5.5

CVSS Score

Published: May 27, 2026 at 12:58 PM UTC

Updated: October 15, 2026 at 02:19 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.1%

Description

In the Linux kernel, the following vulnerability has been resolved: wifi: rtw88: check for PCI upstream bridge existence pci_upstream_bridge() returns NULL if the device is on a root bus. If 8821CE is installed in the system with such a PCI topology, the probing routine will crash. This has probably been unnoticed as 8821CE is mostly supplied in laptops where there is a PCI-to-PCI bridge located upstream from the device. However the card might be installed on a system with different configuration. Check if the bridge does exist for the specific workaround to be applied. Found by Linux Verification Center (linuxtesting.org) with Svace static analysis tool.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

5.15.17 ≤ v < 5.165.16.3 ≤ v < 7.124f5e38a13b5ae2b6105cda8bb47c19108e62a9a5.15.17 5.16.3 5.17617339466fda09916c4b4151fa5e6a9c1fdae353f21e8cb927fa9da49490b74ddda3856a828b82d6

Vendor states this is fixed in 000134a20bbf89b1152520a2eef71f91fdb83a5b (fixed)

Vendor states this is fixed in 3b89b4c095804c478d50376285e66700cf3c045f (fixed)

Vendor states this is fixed in 3bbbb56204f7359ce2139a9341b43b52a186261c (fixed)

Vendor states this is fixed in 6c53d68e3bcfc8faccdd76c3383a9232b05c9ae6 (fixed)

Vendor states this is fixed in 959c13da6c36167ce1016d400a6104d2367f686e (fixed)

Vendor states this is fixed in cc9b6303e7ea91bc360b42c7edc1fe9ceb2f47fe (fixed)

Vendor states this is fixed in eb101d2abdcccb514ca4fccd3b278dd8267374f6 (fixed)

Vendor states this is fixed in 5.15.210 (unaffected)

Affected range stops below 5.16, so it looks safe — our inference, not a vendor statement

Vendor states this is fixed in 5.17 (unaffected)

Vendor states this is fixed in 6.1.175 (unaffected)

Vendor states this is fixed in 6.12.86 (unaffected)