{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2024-46725",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2024-46725"
  ],
  "published": "2024-09-18T06:32:49Z",
  "summary": "drm/amdgpu: Fix out-of-bounds write warning",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu: Fix out-of-bounds write warning\n\nCheck the ring type value to fix the out-of-bounds\nwrite warning",
  "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.109",
            "compiled_filter": false
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2024-46725"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/c253b87c7c37ec40a2e0c84e4a6b636ba5cd66b2"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/919f9bf9997b8dcdc132485ea96121e7d15555f9"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/cf2db220b38301b6486a0f11da24a0f317de558c"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/a60d1f7ff62e453dde2d3b4907e178954d199844"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/130bee397b9cd52006145c87a456fd8719390cb5"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/be1684930f5262a622d40ce7a6f1423530d87f89"
    }
  ],
  "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 defect is in the amdgpu ring/scheduler registration path executed during local device and driver initialization, and the corrupted `gpu_sched[][]` table is consumed only through local DRM ioctls on /dev/dri/card*/renderD*. There is no network or adjacent-network path into amdgpu ring init.\nAC:L - In an affected configuration the ring type is a compile-time constant, so the out-of-bounds index is deterministic on every initialization \u2014 there is no race to win and no memory-layout condition to guess.\nPR:L - No capability check or privilege gate protects the array indexing itself; it runs as part of ordinary device attach/probe, and the resulting scheduler table is subsequently read and dereferenced on behalf of unprivileged local users holding a DRM render-node fd (amdgpu_ctx.c:163/229). Real root in the init namespace is not required to consume the corrupted state.\nUI:N - The write occurs automatically during driver/device initialization and the corrupted table is used by the attacker's own context-creation and command-submission ioctls; no action by another user or victim is needed.\nS:U - The corruption and its consequences are confined to the kernel of the machine running the driver, within `struct amdgpu_device`; no VM, IOMMU, or sandbox boundary is crossed.\nC:H - The code reads a `num_scheds` counter from out-of-bounds memory and uses it as an unbounded write index, and the resulting corruption of adjacent `struct amdgpu_irq` state (interrupt source tables and callback pointers) is memory corruption that can be leveraged for disclosure of kernel memory.\nI:H - This is an out-of-bounds write of a kernel pointer (`&ring->sched`) past `gpu_sched[][]` at an index taken from out-of-bounds memory, overwriting adjacent interrupt-handling structures in `struct amdgpu_device`; per kernel scoring guidance an OOB write with a corrupted destination index is High, as it can be leveraged toward control-flow hijack.\nA:H - Corrupting the scheduler table and adjacent irq structures leaves stale or wild `drm_gpu_scheduler` pointers that are later dereferenced during entity setup and interrupt dispatch, producing a kernel oops and a wedged GPU/system."
    }
  }
}