{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2026-90403",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2026-90403"
  ],
  "published": "2026-09-17T16:10:40Z",
  "summary": "wifi: rtlwifi: pci: fix error path in rtl_pci_probe()",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: rtlwifi: pci: fix error path in rtl_pci_probe()\n\nIn the last error path in rtl_pci_probe(), the cleanup functions are\nskipped due to a wrong goto label. Moreover, the successful call to\nrtl_init_rfkill(), ieee80211_register_hw(), rtl_debug_add_one() have to\nbe reverted. Fix this issue by updating the labels and adding the\nrelevant cleanup functions to the last error path.",
  "severity": [
    {
      "type": "CVSS_V3",
      "score": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H"
    }
  ],
  "affected": [
    {
      "package": {
        "ecosystem": "Raspberry Pi OS:12",
        "name": "linux"
      },
      "versions": [
        "1:6.1.47-1+rpt4"
      ],
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-2712",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v6",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v7",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v7l",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v8",
            "binary_version": "1:6.1.47-1+rpt4"
          }
        ]
      },
      "database_specific": {
        "per_version": {
          "1:6.1.47-1+rpt4": {
            "linux_commit": "655fc658a15ae7a6f37103754adb39ba52a9a14e",
            "upstream_version": "6.1.47",
            "assessment": "commit ancestry (strak rule)",
            "upstream_fixed": "6.1.188",
            "compiled_filter": false
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-90403"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/2634998247d24be34ba16a7666f31815ef1da00b"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/cfd6824dd1d151ab3abc00117b3774c8056006e0"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/86e6187f8525c8f8219eb49e022eba854cc6ab86"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/aef178ffae5420afdbf46f7133ed28bd4248e15c"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/b42fcfb097da46f0e86564736ced939e83cb8442"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/a89818977338ba71194b1ab1d071f0c0848b1e13"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/1b68b6e529ce75112fab98e89583a76370ca394b"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/3c2999d13eeb222ae56631aeb7ca248090f2b210"
    }
  ],
  "database_specific": {
    "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git",
    "upstream_modified": "2026-09-18T17:55:42Z",
    "severity": {
      "source": "kernel CNA",
      "cvss_v3_score": 7.0,
      "cvss_v3_severity": "High",
      "scenario": "AV:L - The UAF is only on rtl_pci_probe()'s last error path, when rtl_pci_intr_mode_decide() fails and the old code jumped to fail3. That path is reached from local_pci_probe() as the .probe of rtl8192ce/rtl8188ee/rtl8192ee/rtl8723be and related pci_driver tables (e.g. Realtek 0x8191/0x8178). 802.11 frames never enter rtl_pci_probe.\nAC:H - The only trigger is pci_enable_msi() or request_irq(pdev->irq, _rtl_pci_interrupt, IRQF_SHARED) failing after ieee80211_register_hw() has already succeeded. pdev->irq is assigned by the host PCI/ACPI code, and the subsequent irqaction kzalloc is tiny compared with earlier ring and wiphy allocations, so an attacker cannot reliably force that failure.\nPR:L - Once fail3 has run ieee80211_free_hw() on the still-registered hw, the leftover default wlan vif from ieee80211_if_add(), cfg80211 wiphy, inetaddr notifiers, and rfkill poll are reachable via nl80211 or any netns address change without init-namespace root or PCI sysfs bind.\nUI:N - No victim must mount media or associate to a network; after the failed probe unwind, the attacker\u2019s own nl80211 use of the leftover wlan vif, an inetaddr change, or cfg80211_rfkill_poll touches the still-registered ieee80211_local.\nS:U - ieee80211_free_hw() frees the still-registered ieee80211_local/wiphy while mac80211 still holds it; impact is host-kernel heap corruption, not a VM, IOMMU, or sandbox escape.\nC:H - fail3 calls ieee80211_free_hw() without ieee80211_unregister_hw(), so cfg80211_rfkill_poll \u2192 ieee80211_rfkill_poll and nl80211 still dereference the kfree'd ieee80211_local, wiphy bands, and default STA vif, a UAF read primitive.\nI:H - The leftover objects are written by ieee80211_ifa_changed (inetaddr notifier), mac80211 workqueues never torn down by ieee80211_unregister_hw(), and rtl_op_rfkill_poll via wiphy_rfkill_start_polling, enabling UAF writes and control-flow hijack.\nA:H - ieee80211_free_hw() without ieee80211_unregister_hw() leaves mac80211 workqueues, inetaddr notifiers, the default wlan vif, and rfkill polling running against freed ieee80211_local, which oopses or panics on the next access."
    }
  }
}