Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-46092wifi: rtw88: check for PCI upstream bridge existence

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.

Timeline

  1. ID reserved

    By Linux

  2. · 14 days later

    Published

  3. · 5 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-46092, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.14% · top 97% of all CVEs (14 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 617339466fda09916c4b4151fa5e6a9c1fdae353 – < 959c13da6c36167ce1016d400a6104d2367f686e
    • affected 24f5e38a13b5ae2b6105cda8bb47c19108e62a9a – < 3b89b4c095804c478d50376285e66700cf3c045f
    • affected 24f5e38a13b5ae2b6105cda8bb47c19108e62a9a – < cc9b6303e7ea91bc360b42c7edc1fe9ceb2f47fe
    • affected 24f5e38a13b5ae2b6105cda8bb47c19108e62a9a – < 6c53d68e3bcfc8faccdd76c3383a9232b05c9ae6
    • affected 24f5e38a13b5ae2b6105cda8bb47c19108e62a9a – < 000134a20bbf89b1152520a2eef71f91fdb83a5b
    • affected 24f5e38a13b5ae2b6105cda8bb47c19108e62a9a – < 3bbbb56204f7359ce2139a9341b43b52a186261c
    • affected 24f5e38a13b5ae2b6105cda8bb47c19108e62a9a – < eb101d2abdcccb514ca4fccd3b278dd8267374f6
    • affected f21e8cb927fa9da49490b74ddda3856a828b82d6
    • affected 5.15.17 – < 5.15.210
    • affected 5.16.3 – < 5.17
  • Linux · Linux

    • affected 5.17
    • unaffected < 5.17
    • unaffected 5.15.210 – ≤ 5.15.*
    • unaffected 6.1.175 – ≤ 6.1.*
    • unaffected 6.6.140 – ≤ 6.6.*
    • unaffected 6.12.86 – ≤ 6.12.*
    • unaffected 6.18.27 – ≤ 6.18.*
    • unaffected 7.0.4 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-46092 badge
[![CVE-2026-46092](https://cveledger.app/badge/CVE-2026-46092.svg)](https://cveledger.app/cve/CVE-2026-46092)

Record last updated .