{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2024-38569",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2024-38569"
  ],
  "published": "2024-06-19T13:36:08Z",
  "summary": "drivers/perf: hisi_pcie: Fix out-of-bound access when valid event group",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrivers/perf: hisi_pcie: Fix out-of-bound access when valid event group\n\nThe perf tool allows users to create event groups through following\ncmd [1], but the driver does not check whether the array index is out of\nbounds when writing data to the event_group array. If the number of events\nin an event_group is greater than HISI_PCIE_MAX_COUNTERS, the memory write\noverflow of event_group array occurs.\n\nAdd array index check to fix the possible array out of bounds violation,\nand return directly when write new events are written to array bounds.\n\nThere are 9 different events in an event_group.\n[1] perf stat -e '{pmu/event1/, ... ,pmu/event9/}'",
  "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.93",
            "compiled_filter": false
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2024-38569"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/3d1face00ebb7996842aee4214d7d0fb0c77b1e9"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/8e9aab2492178f25372f1820bfd9289fbd74efd0"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/567d34626c22b36579ec0abfdf5eda2949044220"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/ff48247144d13a3a0817127703724256008efa78"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/77fce82678ea5fd51442e62febec2004f79e041b"
    }
  ],
  "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 bug is reached only through the local `perf_event_open(2)` syscall against a HiSilicon PCIe PMU device; no network or remote-peer data is involved.\nAC:L - Triggering is fully deterministic \u2014 open a group leader plus 7 distinct hisi_pcie events, then open a 9th distinct event \u2014 with no race, timing window, or memory-layout condition outside the attacker's control.\nPR:L - On the profiling/HPC/Kunpeng-server deployments where this PMU driver is actually used, `kernel.perf_event_paranoid` is commonly set to 0 or -1, which makes `perf_allow_cpu()` pass for any unprivileged local user; only that (not real root) is needed to build the oversized event group.\nUI:N - The attacker performs the entire nine-syscall sequence itself; no victim action or cooperation is required.\nS:U - The out-of-bounds write corrupts the kernel's own stack within the same security authority; no VM, IOMMU, or sandbox boundary is crossed.\nC:H - The overflow is stack memory corruption adjacent to saved registers and spilled pointers, which per kernel scoring practice can be leveraged toward disclosure of kernel memory and defeats stack-layout confidentiality assumptions.\nI:H - This is an out-of-bounds stack write that places an attacker-groomed kernel heap pointer over the canary/saved-register slot above the array, i.e. corruption of control-flow-relevant stack state.\nA:H - On stack-protector-enabled arm64 builds the OOB write clobbers the canary and reliably triggers `__stack_chk_fail()` \u2192 kernel panic, and it can be repeated at will from userspace."
    }
  }
}