{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2024-26664",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2024-26664"
  ],
  "published": "2024-04-02T06:22:38Z",
  "summary": "hwmon: (coretemp) Fix out-of-bounds memory access",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nhwmon: (coretemp) Fix out-of-bounds memory access\n\nFix a bug that pdata->cpu_map[] is set before out-of-bounds check.\nThe problem might be triggered on systems with more than 128 cores per\npackage.",
  "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.78",
            "compiled_filter": false
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2024-26664"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/93f0f4e846fcb682c3ec436e3b2e30e5a3a8ee6a"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/1eb74c00c9c3b13cb65e508c5d5a2f11afb96b8b"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/f0da068c75c20ffc5ba28243ff577531dc2af1fd"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/a16afec8e83c56b14a4a73d2e3fb8eec3a8a057e"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/9bce69419271eb8b2b3ab467387cb59c99d80deb"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/853a6503c586a71abf27e60a7f8c4fb28092976d"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/3a7753bda55985dc26fae17795cb10d825453ad1"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/4e440abc894585a34c2904a32cd54af1742311b3"
    }
  ],
  "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 - `create_core_data()` is only reachable through the coretemp CPU-hotplug callback (`coretemp_cpu_online()`), exercised at module load/boot and on local `/sys/devices/system/cpu/cpuN/online` writes. There is no network, adjacent-network, or removable-device path into this hwmon driver.\nAC:L - On an affected target (an Intel package with more than 128 cores, e.g. 144-core Sierra Forest sockets) the out-of-bounds write is fully deterministic \u2014 it fires on every boot and on every CPU-online cycle once the IDA index passes 127, with no race, no grooming, and no per-attempt uncertainty. Target-configuration/hardware dependence is not AC:H under CVSS 3.1.\nPR:L - The driver performs no capability or credential check anywhere on the `coretemp_cpu_online()` \u2192 `coretemp_add_core()` \u2192 `create_core_data()` path; the corruption occurs during ordinary CPU bring-up with no privilege held at all, and the runtime re-trigger is CPU hotplug. Scoring the more severe of the arguable options (boot/module-load-reachable by a low-privileged local presence) rather than requiring full root.\nUI:N - CPU onlining and coretemp initialization happen automatically as part of normal system startup and hotplug handling. No victim action of any kind is required.\nS:U - The out-of-bounds write corrupts fields inside the kernel's own `struct platform_data` allocation and the follow-on damage stays in kernel slab memory on the same host. No VM, IOMMU, or sandbox security boundary is crossed.\nC:H - Indices 135\u2013138 overwrite `ida.xa.xa_head` two bytes at a time, leaving a near-valid kernel pointer that the next `ida_alloc_range()` dereferences via `xas_find_marked()`/`find_next_zero_bit()`, reading arbitrary kernel slab memory as an `xa_node`/`ida_bitmap`. The corrupted `pd->cpumask` also redirects `rdmsr_on_cpu()` targets for the sysfs temperature readers.\nI:H - This is an out-of-bounds write that clobbers a live kernel pointer, the xarray spinlock and flags, and the CPU mask inside `struct platform_data`. The resulting type confusion lets `__set_bit()` in `ida_alloc_range()` write into misinterpreted kernel memory, and corrupted `core_data[]`/cpumask state can drive bogus `kfree()` and stale-sysfs teardown in `coretemp_remove_core()`.\nA:H - Once `xa_head` is corrupted, the next IDA operation walks a garbage or non-canonical pointer, producing an immediate oops or GP fault; corrupting the xarray spinlock can also wedge the hotplug path. Any of these is a kernel crash or hang."
    }
  }
}