{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2024-46815",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2024-46815"
  ],
  "published": "2024-09-27T12:36:20Z",
  "summary": "drm/amd/display: Check num_valid_sets before accessing reader_wm_sets[]",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/display: Check num_valid_sets before accessing reader_wm_sets[]\n\n[WHY & HOW]\nnum_valid_sets needs to be checked to avoid a negative index when\naccessing reader_wm_sets[num_valid_sets - 1].\n\nThis fixes an OVERRUN issue reported by Coverity.",
  "severity": [
    {
      "type": "CVSS_V3",
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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.109",
            "compiled_filter": false
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2024-46815"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/a72d4996409569027b4609414a14a87679b12267"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/7c47dd2e92341f2989ab73dbed07f8894593ad7b"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/c4a7f7c0062fe2c73f70bb7e335199e25bd71492"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/b36e9b3104c4ba0f2f5dd083dcf6159cb316c996"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/21f9cb44f8c60bf6c26487d428b1a09ad3e8aebf"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/6a4a08e45e614cfa7a56498cdfaeb7fae2f07fa0"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/b38a4815f79b87efb196cd5121579fc51e29a7fb"
    }
  ],
  "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.1,
      "cvss_v3_severity": "High",
      "scenario": "AV:L - The affected code is amdgpu display clock-manager init for DCN2.1 (Renoir/Cezanne APUs), reached only through local GPU bring-up \u2014 driver probe and `dc_set_power_state(D0)` on system/runtime-PM resume \u2014 with no network, packet, or remote-peer input anywhere on the path. Local is selected over Physical as the higher-severity of the two defensible options.\nAC:L - Once a platform presents the anomalous watermark table (first valid entry typed `WM_TYPE_RETRAINING`), the negative-index write occurs deterministically on every `rn_notify_wm_ranges()` call \u2014 there is no race, timing window, or memory-layout condition outside the attacker's control. Chosen as the higher-severity option even though the driver's own table-population code cannot produce that state.\nPR:L - On an affected platform the vulnerable path is re-entered on every GPU D0 transition, and an unprivileged local user holding `/dev/dri/cardN` (normal desktop/kiosk seat access) can force repeated runtime suspend/resume cycles to re-run `dcn10_init_hw()` \u2192 `rn_notify_wm_ranges()`. No root, CAP_SYS_ADMIN, or namespace privilege is needed to reach the code.\nUI:N - The attacker drives the GPU power-state transitions themselves via their own DRM device access; no separate victim has to log in, open a file, or perform any action.\nS:U - The corrupted memory is the kernel's own `struct clk_mgr_internal` allocation inside the amdgpu driver, so the fault and its impact stay within the kernel's security authority \u2014 no VM, IOMMU, or sandbox boundary is crossed.\nC:N - The defect is a write of the fixed constant `PP_SMU_WM_SET_RANGE_CLK_UNCONSTRAINED_MAX` (0xFFFF) to a fixed negative offset; there is no out-of-bounds read, no attacker-chosen address, and no value returned to userspace or any observable channel.\nI:H - This is an out-of-bounds (negative-index) write that lands squarely on the upper half of the live `clk_mgr->bw_params` kernel pointer, corrupting kernel state that is dereferenced repeatedly afterwards by the clock manager and DML code. Per kernel scoring guidance, an out-of-bounds write is High.\nA:H - After the write, `bw_params` is a wild pointer dereferenced throughout `rn_clk_mgr`/DML on every clock update, producing an oops or panic; because it recurs on each GPU resume, the system is left unusable rather than transiently degraded."
    }
  }
}