{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2024-46813",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2024-46813"
  ],
  "published": "2024-09-27T12:36:20Z",
  "summary": "drm/amd/display: Check link_index before accessing dc->links[]",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/display: Check link_index before accessing dc->links[]\n\n[WHY & HOW]\ndc->links[] has max size of MAX_LINKS and NULL is return when trying to\naccess with out-of-bound index.\n\nThis fixes 3 OVERRUN and 1 RESOURCE_LEAK issues reported by Coverity.",
  "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": null,
            "compiled_filter": false
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2024-46813"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/032c5407a608ac3b2a98bf4fbda27d12c20c5887"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/ac04759b4a002969cf0f1384f1b8bb2001cfa782"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/8aa2864044b9d13e95fe224f32e808afbf79ecdf"
    }
  ],
  "database_specific": {
    "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git",
    "upstream_modified": "2026-08-05T11:52:36Z",
    "severity": {
      "source": "kernel CNA",
      "cvss_v3_score": 7.8,
      "cvss_v3_severity": "High",
      "scenario": "AV:L - The vulnerable code is in the amdgpu DC display driver, reached during local driver probe and subsequently exercised through the local DRM device node (/dev/dri/card*) via atomic ioctl HDCP operations. There is no network-facing path to dc_get_link_at_index().\nAC:L - On an affected platform (DCN3.1-class hardware with 4 USB4 DPIA links plus a VBIOS reporting enough connector indices to push link_count past MAX_LINKS) the out-of-bounds access occurs deterministically on every driver load, and the subsequent use of the corrupted ddc.handle is reached reliably by enabling HDCP. No unpredictable memory-layout or timing condition must be won.\nPR:L - The out-of-bounds read and type-confused write occur during unprivileged driver initialization, and the corrupted HDCP DDC handle is subsequently dereferenced through the Content Protection connector property, which a local user with access to /dev/dri can set via the DRM atomic ioctl. No root or CAP_SYS_ADMIN is required.\nUI:N - The out-of-bounds indexing happens automatically at driver probe with no victim action, and the follow-on HDCP DDC path is driven entirely by the attacker's own DRM ioctls.\nS:U - The out-of-bounds access and the resulting corruption are confined to kernel memory within the same security authority; no VM, IOMMU, or sandbox boundary is crossed.\nC:H - The out-of-bounds read pulls adjacent struct dc members (link_srv, current_state, res_pool, clk_mgr) and treats them as a struct dc_link, so subsequent field reads and the HDCP DDC read_dpcd/read_i2c calls interpret arbitrary kernel memory as link state, and the resulting memory corruption can be leveraged for further information disclosure.\nI:H - The type-confused pointer is written through (link->priv = aconnector, link->psr_settings.* = ...), corrupting a live kernel object such as struct link_service or dc_state that contains function pointers, giving a memory-corruption primitive exploitable for control-flow hijacking.\nA:H - Dereferencing an out-of-bounds pointer read as a struct dc_link, and corrupting adjacent live kernel structures, reliably produces a kernel oops/panic and leaves the display subsystem in an inconsistent state."
    }
  }
}