{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2024-46811",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2024-46811"
  ],
  "published": "2024-09-27T12:36:20Z",
  "summary": "drm/amd/display: Fix index may exceed array range within fpu_update_bw_bounding_box",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/display: Fix index may exceed array range within fpu_update_bw_bounding_box\n\n[Why]\nCoverity reports OVERRUN warning. soc.num_states could\nbe 40. But array range of bw_params->clk_table.entries is 8.\n\n[How]\nAssert if soc.num_states greater than 8.",
  "severity": [
    {
      "type": "CVSS_V3",
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/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-46811"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/4003bac784380fed1f94f197350567eaa73a409d"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/aba188d6f4ebaf52acf13f204db2bd2c22072504"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/188fd1616ec43033cedbe343b6579e9921e2d898"
    }
  ],
  "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.3,
      "cvss_v3_severity": "High",
      "scenario": "AV:L - The vulnerable code is reached only through amdgpu DC initialization paths on the local machine \u2014 `dc_construct()`, `dcn32_init_hw()`, and `get_memclk_states_from_smu()` during hardware init and suspend/resume. There is no network, adjacent-network, or physical-device vector.\nAC:L - On affected hardware the overrun happens deterministically whenever the firmware-reported DPM level count plus the hardcoded DCFCLK STA targets exceeds 8 \u2014 no race to win, no memory layout to groom, and no unlikely precondition. The vulnerable path in dcn302/dcn303 is entirely ungated.\nPR:L - The trigger points (DC hardware init and resume of the DRM device) are reachable in an ordinary unprivileged desktop session via logind-mediated suspend/resume of the GPU, without root in the init namespace. No pre-authentication or remote path exists, so PR:N is not supportable.\nUI:N - The bounding-box update runs automatically during driver hardware init and resume; no victim action such as opening a file or plugging in a display is required.\nS:U - The out-of-bounds read and the resulting corrupted DML bounding box are both entirely within the kernel's own security authority \u2014 there is no VM, IOMMU, or sandbox boundary crossed.\nC:H - With `num_states` able to reach `DC__VOLTAGE_STATES` (40) against an 8-element `entries[]`, the read runs up to ~1.3 KB past the end of the `struct clk_bw_params` allocation into adjacent slab memory \u2014 far beyond a \"few bytes\" bounded read. Those bytes are copied into `dml.soc.clock_limits[]`, which feeds userspace-observable clock and mode-validation state.\nI:L - There is no out-of-bounds write \u2014 `clock_limits[]` is 40 entries and the index is bounded by that \u2014 but attacker-uncontrolled garbage from adjacent memory is written into the DML soc bounding box and then used to program dispclk/dppclk/dcfclk/socclk, corrupting kernel state that drives real display hardware.\nA:H - Reading past the end of the heap-allocated `clk_bw_params` can fault or oops and reliably trips KASAN, and feeding nonsensical clock/voltage limits into DML can hang or blank the display pipeline. Any such kernel crash or hang is High."
    }
  }
}