{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2026-74413",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2026-74413"
  ],
  "published": "2026-08-15T06:04:33Z",
  "summary": "wifi: rtw89: fix wrong pci_get_drvdata type in AER handlers",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: rtw89: fix wrong pci_get_drvdata type in AER handlers\n\nrtw89 stores an ieee80211_hw pointer via pci_set_drvdata() at probe\ntime, but io_error_detected() and io_resume() retrieve it as a\nnet_device pointer.  This causes netif_device_detach/attach to\noperate on an ieee80211_hw struct, reading and writing at wrong\noffsets.  The adjacent io_slot_reset() already does it correctly.\n\nUse ieee80211_stop_queues/wake_queues instead, consistent with\nevery other queue stop/start path in the driver.\n\nTested on RTL8852CE by calling the handlers from a test module\nbefore and after the fix.",
  "severity": [
    {
      "type": "CVSS_V3",
      "score": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
    }
  ],
  "affected": [
    {
      "package": {
        "ecosystem": "Raspberry Pi OS:13",
        "name": "linux"
      },
      "versions": [
        "1:6.18.29-1+rpt1",
        "1:6.18.33-1+rpt1",
        "1:6.18.34-1+rpt1",
        "1:6.18.39-1+rpt1"
      ],
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-image-6.18.29+rpt-rpi-2712",
            "binary_version": "1:6.18.29-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.29+rpt-rpi-v8",
            "binary_version": "1:6.18.29-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.29+rpt-rpi-v8-rt",
            "binary_version": "1:6.18.29-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.33+rpt-rpi-2712",
            "binary_version": "1:6.18.33-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.33+rpt-rpi-v8",
            "binary_version": "1:6.18.33-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.33+rpt-rpi-v8-rt",
            "binary_version": "1:6.18.33-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.34+rpt-rpi-2712",
            "binary_version": "1:6.18.34-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.34+rpt-rpi-v8",
            "binary_version": "1:6.18.34-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.34+rpt-rpi-v8-rt",
            "binary_version": "1:6.18.34-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.39+rpt-rpi-2712",
            "binary_version": "1:6.18.39-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.39+rpt-rpi-v8",
            "binary_version": "1:6.18.39-1+rpt1"
          },
          {
            "binary_name": "linux-image-6.18.39+rpt-rpi-v8-rt",
            "binary_version": "1:6.18.39-1+rpt1"
          }
        ]
      },
      "database_specific": {
        "per_version": {
          "1:6.18.29-1+rpt1": {
            "linux_commit": "66318c5b5cd8145a662303af12ed39ac07eb27cc",
            "upstream_version": "6.18.29",
            "assessment": "commit ancestry (strak rule)",
            "upstream_fixed": "6.18.40"
          },
          "1:6.18.33-1+rpt1": {
            "linux_commit": "95b85bebbedcaedfa7ca79116ed38b7376fba412",
            "upstream_version": "6.18.33",
            "assessment": "commit ancestry (strak rule)",
            "upstream_fixed": "6.18.40"
          },
          "1:6.18.34-1+rpt1": {
            "linux_commit": "c8c7494100e99ee05b11aaa4f0588a223a63d1af",
            "upstream_version": "6.18.34",
            "assessment": "commit ancestry (strak rule)",
            "upstream_fixed": "6.18.40"
          },
          "1:6.18.39-1+rpt1": {
            "linux_commit": "60ea684a8ace97bb0db1a16e20753bdd6ab371ff",
            "upstream_version": "6.18.39",
            "assessment": "commit ancestry (strak rule)",
            "upstream_fixed": "6.18.40"
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-74413"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/aefc30e4a829c1683f6ae999df7f9310c27eae6c"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/c1907b9a4fa9cb33d11a9af138374dd2e93f7a93"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/7068c379cf9aa8afe4dce4d9d82390187aa9c4d0"
    }
  ],
  "database_specific": {
    "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git",
    "upstream_modified": "2026-08-17T05:50:24Z",
    "severity": {
      "source": "kernel CNA",
      "cvss_v3_score": 8.8,
      "cvss_v3_severity": "High",
      "scenario": "AV:A - The vulnerable rtw89 PCIe AER handlers run when the adapter reports non-fatal/fatal PCIe errors; on laptops with RTL8852CE/8852BE and similar in public wireless environments, an adjacent attacker can plausibly induce link faults via traffic stressing the radio-PCIe path.\nAC:L - Once AER recovery invokes rtw89_pci_io_error_detected/resume, the type confusion deterministically treats ieee80211_hw as net_device and corrupts memory through netif_device_detach/attach; no race or layout guesswork beyond triggering PCIe recovery is needed.\nPR:N - No local OS privileges or capabilities are required; an adjacent wireless attacker targeting a victim's rtw89 PCIe WiFi can enter the faulty AER recovery path without authenticating to or holding an account on the system.\nUI:N - No victim action beyond normal use of the affected rtw89 WiFi interface is required; PCIe AER recovery and the corruption run automatically in kernel interrupt/workqueue context.\nS:U - Type confusion corrupts kernel memory within the same kernel security authority; no VM, container, or IOMMU boundary is crossed.\nC:H - Casting ieee80211_hw to net_device makes netif_device_detach/attach read state, flags, and queue metadata at wrong offsets, constituting type confusion that can disclose adjacent kernel memory per kernel CVSS guidance.\nI:H - Atomic bit clears/sets and netif_tx_stop/wake queue operations run on ieee80211_hw memory misinterpreted as net_device fields, enabling out-of-bounds writes and exploitable memory corruption warranting High integrity impact.\nA:H - Misinterpreting ieee80211_hw as net_device leads netif_tx_stop_all_queues and netdev_watchdog_up to dereference garbage queue pointers, causing kernel oops/panic during AER recovery with High availability impact."
    }
  }
}
