{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2023-52777",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2023-52777"
  ],
  "published": "2024-05-21T15:34:20Z",
  "summary": "wifi: ath11k: fix gtk offload status event locking",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nwifi: ath11k: fix gtk offload status event locking\n\nThe ath11k active pdevs are protected by RCU but the gtk offload status\nevent handling code calling ath11k_mac_get_arvif_by_vdev_id() was not\nmarked as a read-side critical section.\n\nMark the code in question as an RCU read-side critical section to avoid\nany potential use-after-free issues.\n\nCompile tested only.",
  "severity": [
    {
      "type": "CVSS_V3",
      "score": "CVSS:3.1/AV:L/AC:L/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.64",
            "compiled_filter": false
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2023-52777"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/0cf7577b6b3153b4b49deea9719fe43f96469c6d"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/cf9c7d783a2bf9305df4ef5b93d9063a52e18fca"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/e83246ecd3b193f8d91fce778e8a5ba747fc7d8a"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/1dea3c0720a146bd7193969f2847ccfed5be2221"
    }
  ],
  "database_specific": {
    "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git",
    "upstream_modified": "2026-08-05T11:24:39Z",
    "severity": {
      "source": "kernel CNA",
      "cvss_v3_score": 7.8,
      "cvss_v3_severity": "High",
      "scenario": "AV:L - The handler runs on a host-solicited WMI_GTK_OFFLOAD_STATUS_EVENT from ath11k_wmi_gtk_rekey_getinfo() during WoW resume, not on parsing over-the-air 802.11 frames; like the htt pktlog sibling, triggering requires local suspend/resume on the ath11k host.\nAC:L - A local attacker can drive both sides of the missing-RCU race by inducing WoW resume (async getinfo status event) while concurrently stopping/rfkilling the radio so mac_op_stop clears pdevs_active without waiting for the unlocked reader.\nPR:L - Unlike pktlog (root-only debugfs), GTK offload status is reached through normal WoW suspend/resume on an already-associated STA, and a basic local seat user can suspend and rfkill/tear down wifi without real root; choose Low over High under uncertainty.\nUI:N - The attacker triggers suspend/resume and concurrent radio teardown themselves; no separate victim action such as mounting a device or opening a file is required.\nS:U - Any use-after-free or crash remains inside the host kernel ath11k/mac80211 authority and does not cross a VM, IOMMU, or sandbox boundary.\nC:H - Missing rcu_read_lock around ath11k_mac_get_arvif_by_vdev_id() allows use of RCU-protected pdev/arvif state after deactivation/teardown; per guidance that UAF enables heap reuse and arbitrary kernel disclosure.\nI:H - The same UAF of sprayable ath11k/ieee80211 state while the handler still writes arvif->rekey_data and calls ieee80211_gtk_rekey_notify() yields write/control-flow primitives characteristic of exploitable kernel UAFs.\nA:H - Concurrent use of deactivated or freed ar/arvif after synchronize_rcu without a matching read-side critical section can oops/panic the kernel, so availability impact is complete even without full code execution."
    }
  }
}
