{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2023-52864",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2023-52864"
  ],
  "published": "2024-05-21T15:34:20Z",
  "summary": "platform/x86: wmi: Fix opening of char device",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nplatform/x86: wmi: Fix opening of char device\n\nSince commit fa1f68db6ca7 (\"drivers: misc: pass miscdevice pointer via\nfile private data\"), the miscdevice stores a pointer to itself inside\nfilp->private_data, which means that private_data will not be NULL when\nwmi_char_open() is called. This might cause memory corruption should\nwmi_char_open() be unable to find its driver, something which can\nhappen when the associated WMI device is deleted in wmi_free_devices().\n\nFix the problem by using the miscdevice pointer to retrieve the WMI\ndevice data associated with a char device using container_of(). This\nalso avoids wmi_char_open() picking a wrong WMI device bound to a\ndriver with the same name as the original driver.",
  "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.63",
            "compiled_filter": false
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2023-52864"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/cf098e937dd125c0317a0d6f261ac2a950a233d6"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/9fb0eed09e1470cd4021ff52b2b9dfcbcee4c203"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/d426a2955e45a95b2282764105fcfb110a540453"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/e0bf076b734a2fab92d8fddc2b8b03462eee7097"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/44a96796d25809502c75771d40ee693c2e44724e"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/36d85fa7ae0d6be651c1a745191fa7ef055db43e"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/fb7b06b59c6887659c6ed0ecd3110835eecbb6a3"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/eba9ac7abab91c8f6d351460239108bef5e7a0b6"
    }
  ],
  "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.0,
      "cvss_v3_severity": "High",
      "scenario": "AV:L - The bug is reached by opening the local misc char device `/dev/wmi/$driver` (typically `/dev/wmi/dell-smbios`): open \u2192 misc_open \u2192 wmi_char_open. There is no network or adjacent-link path into this platform/x86 WMI code.\nAC:H - Memory corruption requires wmi_char_open() to fail its driver lookup while misc_open still succeeds, which the fix ties to wmi_free_devices() list_del before misc_deregister\u2014i.e. concurrent ACPI/platform WMI removal (e.g. rmmod wmi). An unprivileged attacker can spam open/ioctl but cannot induce that privileged teardown, matching other module-unload races scored AC:H.\nPR:L - The char device is registered with mode 0444, so any local unprivileged user can open it and issue read/ioctl; no init-namespace root or capability is required on the attacker\u2019s side of the race.\nUI:N - The attacker opens and operates on the WMI char device in their own process; no victim action is required. Concurrent administrative device removal is Attack Complexity, not User Interaction.\nS:U - Type confusion / use-after-free stays inside the host kernel\u2019s WMI/misc authority and does not cross a VM, IOMMU, or sandbox boundary.\nC:H - Failed lookup leaves filp->private_data as a miscdevice* that read/ioctl treat as struct wmi_block, causing out-of-bounds reads of adjacent heap; if the wblock is freed while the fd is held this becomes a UAF disclosure primitive, scored High per kernel guidance.\nI:H - The same type confusion/UAF makes wmi_ioctl() mutex_lock, dereference handler_data, and copy_from_user() through misinterpreted pointers\u2014yielding heap corruption and an arbitrary-write primitive after reclaim, so Integrity is High.\nA:H - Misinterpreting a miscdevice as a wmi_block (or using a freed wblock) reliably leads to invalid memory access, oops/panic, or hang on corrupted locks; any such kernel crash/UAF is Availability High."
    }
  }
}