{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2023-52662",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2023-52662"
  ],
  "published": "2024-05-17T13:41:49Z",
  "summary": "drm/vmwgfx: fix a memleak in vmw_gmrid_man_get_node",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/vmwgfx: fix a memleak in vmw_gmrid_man_get_node\n\nWhen ida_alloc_max fails, resources allocated before should be freed,\nincluding *res allocated by kmalloc and ttm_resource_init.",
  "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.83",
            "compiled_filter": false
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2023-52662"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/03b1072616a8f7d6e8594f643b416a9467c83fbf"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/40624af6674745e174c754a20d7c53c250e65e7a"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/83e0f220d1e992fa074157fcf14945bf170ffbc5"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/6fc6233f6db1579b69b54b44571f1a7fde8186e6"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/d1e546ab91c670e536a274a75481034ab7534876"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/89709105a6091948ffb6ec2427954cbfe45358ce"
    }
  ],
  "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 vulnerable GMR/MOB ID allocator is reached only via local DRM ioctls on the vmwgfx device (e.g. DRM_VMW_GB_SURFACE_CREATE / surface validate into VMW_PL_MOB), not via network packet processing.\nAC:L - An attacker can reliably exhaust the finite MOB/GMR ID space (~53K IDs) with repeated small surface/buffer allocations, after which each failed ida_alloc_max path leaks an LRU-linked resource under full attacker control.\nPR:L - The triggering ioctls are marked DRM_RENDER_ALLOW and are usable by an unprivileged local user with access to the DRM render node (/dev/dri/renderD*), without CAP_SYS_ADMIN or DRM master.\nUI:N - Exploitation requires only the attacker's own open/ioctl sequence against the render node; no action by another user is needed.\nS:U - Impact is confined to the guest kernel's TTM/DRM authority (memory leak and UAF in the same kernel); this does not cross a VM/host or other security boundary by itself.\nC:H - Skipping ttm_resource_fini leaves an orphaned ttm_resource on the manager LRU with a raw pointer to the BO; after the BO is freed, eviction/LRU walks (ttm_mem_evict_first) dereference the dangling res->bo, yielding a UAF that can be leveraged for arbitrary read.\nI:H - The same orphaned-LRU UAF against a freed BO is exploitable for heap reuse and write/control-flow hijacking primitives once the attacker triggers eviction after destroying the referenced buffer object.\nA:H - The UAF on LRU walk can oops/panic the kernel, and the unbounded per-failure leak of ttm_resource objects after ID exhaustion can also drive the system to OOM."
    }
  }
}