wifi: rtw88: check for PCI upstream bridge existence
Summary
| CVE | CVE-2026-46092 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-05-27 14:17:30 UTC |
| Updated | 2026-05-27 14:48:03 UTC |
| 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. |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected 24f5e38a13b5ae2b6105cda8bb47c19108e62a9a eb101d2abdcccb514ca4fccd3b278dd8267374f6 git |
Not specified |
| CNA |
Linux |
Linux |
affected 617339466fda09916c4b4151fa5e6a9c1fdae353 git |
Not specified |
| CNA |
Linux |
Linux |
affected f21e8cb927fa9da49490b74ddda3856a828b82d6 git |
Not specified |
| CNA |
Linux |
Linux |
affected 5.15.17 5.16 semver |
Not specified |
| CNA |
Linux |
Linux |
affected 5.16.3 5.17 semver |
Not specified |
| CNA |
Linux |
Linux |
affected 5.17 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 5.17 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.1-rc1 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/eb101d2abdcccb514ca4fccd3b278dd8267374f6 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.