{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2024-46730",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2024-46730"
  ],
  "published": "2024-09-18T06:32:49Z",
  "summary": "drm/amd/display: Ensure array index tg_inst won't be -1",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/display: Ensure array index tg_inst won't be -1\n\n[WHY & HOW]\ntg_inst will be a negative if timing_generator_count equals 0, which\nshould be checked before used.\n\nThis fixes 2 OVERRUN 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-46730"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/15403445b873a4ce45b2d4ecfb5928a025297282"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/a64284b9e1999ad5580debced4bc6d6adb28aad4"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/687fe329f18ab0ab0496b20ed2cb003d4879d931"
    }
  ],
  "database_specific": {
    "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git",
    "upstream_modified": "2026-10-03T11:04:09Z",
    "severity": {
      "source": "kernel CNA",
      "cvss_v3_score": 7.8,
      "cvss_v3_severity": "High",
      "scenario": "AV:L - The vulnerable code is reached only through DRM modeset ioctls on /dev/dri/card* (DRM_IOCTL_MODE_ATOMIC / SETCRTC) via amdgpu_dm_atomic_check() \u2192 dc_state_add_stream() \u2192 resource_map_pool_resources(). No network or remote input reaches this path.\nAC:L - Within an affected resource-pool configuration the negative index is taken deterministically on every stream-add whose pipe_idx exceeds timing_generator_count; there is no race to win and no memory-layout condition the attacker must guess, and the attacker chooses when to issue the modeset.\nPR:L - A local unprivileged user with a DRM fd holding master \u2014 the ordinary case for a logged-in console/graphical session, an Android compositor client, or a kiosk display stack \u2014 can issue the atomic modeset; no capability check exists anywhere on the path from the ioctl to acquire_otg_master_pipe_for_stream().\nUI:N - The attacker performs the modeset/stream-add entirely on their own; no action by another user or administrator is required.\nS:U - The corruption and its consequences stay inside the kernel's amdgpu display driver under the same security authority; no VM, IOMMU, or sandbox boundary is crossed.\nC:H - The \u22121 index reads pointers outside the intended arrays and installs them as wrongly-typed objects, so subsequent accesses read struct fields (funcs, inst, dc_context contents) at mismatched offsets from adjacent kernel objects, exposing kernel pointers and enabling further disclosure through the type-confused reads.\nI:H - stream_res.opp \u2014 actually a struct dpp * \u2014 is written through (opp->mpcc_disconnect_pending[] stores and mpc_tree_params list manipulation corrupt the DPP object), and both stream_res.tg->funcs and stream_res.opp->funcs are read from offsets holding non-vtable data, including gamma-LUT bytes supplied by userspace, giving an indirect call through attacker-influenced memory and thus a control-flow hijack primitive.\nA:H - At minimum the wrongly-typed or NULL pointer is dereferenced and called through during pipe programming, producing an immediate kernel oops/panic in the display pipeline, repeatable at will by the local attacker."
    }
  }
}