Vulnerability · Published Dec 27, 2024 · Assigned by Linux

CVE-2024-56617cacheinfo: Allocate memory during CPU hotplug if not done from the primary CPU

Medium 5.5

In plain English

A medium-severity null pointer dereference in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 11% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)5.5Medium
Exploit odds (30 days)0.2%top 89.3% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official description

In the Linux kernel, the following vulnerability has been resolved: cacheinfo: Allocate memory during CPU hotplug if not done from the primary CPU Commit 5944ce092b97 ("arch_topology: Build cacheinfo from primary CPU") adds functionality that architectures can use to optionally allocate and build cacheinfo early during boot. Commit 6539cffa9495 ("cacheinfo: Add arch specific early level initializer") lets secondary CPUs correct (and reallocate memory) cacheinfo data if needed. If the early build functionality is not used and cacheinfo does not need correction, memory for cacheinfo is never allocated. x86 does not use the early build functionality. Consequently, during the cacheinfo CPU hotplug callback, last_level_cache_is_valid() attempts to dereference a NULL pointer: BUG: kernel NULL pointer dereference, address: 0000000000000100 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not present page PGD 0 P4D 0 Oops: 0000 [#1] PREEPMT SMP NOPTI CPU: 0 PID 19 Comm: cpuhp/0 Not tainted 6.4.0-rc2 #1 RIP: 0010: last_level_cache_is_valid+0x95/0xe0a Allocate memory for cacheinfo during the cacheinfo CPU hotplug callback if not done earlier. Moreover, before determining the validity of the last-level cache info, ensure that it has been allocated. Simply checking for non-zero cache_leaves() is not sufficient, as some architectures (e.g., Intel processors) have non-zero cache_leaves() before allocation. Dereferencing NULL cacheinfo can occur in update_per_cpu_data_slice_size(). This function iterates over all online CPUs. However, a CPU may have come online recently, but its cacheinfo may not have been allocated yet. While here, remove an unnecessary indentation in allocate_cache_info(). [ bp: Massage. ]

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:13linux6.12.5-1DEBIAN-CVE-2024-56617
Debian:14linux6.12.5-1DEBIAN-CVE-2024-56617
Ubuntu:24.04:LTSlinuxno fix listedUBUNTU-CVE-2024-56617
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2024-56617
Ubuntu:24.04:LTSlinux-awsno fix listedUBUNTU-CVE-2024-56617
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2024-56617
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2024-56617
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2024-56617
Ubuntu:22.04:LTSlinux-aws-6.8no fix listedUBUNTU-CVE-2024-56617
Ubuntu:24.04:LTSlinux-azureno fix listedUBUNTU-CVE-2024-56617
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2024-56617
Ubuntu:24.04:LTSlinux-azure-6.116.11.0-1012.12~24.04.1UBUNTU-CVE-2024-56617
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2024-56617
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2024-56617
Ubuntu:22.04:LTSlinux-azure-6.8no fix listedUBUNTU-CVE-2024-56617
Ubuntu:24.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2024-56617
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2024-56617
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2024-56617
Ubuntu:22.04:LTSlinux-azure-fde-6.8no fix listedUBUNTU-CVE-2024-56617
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2024-56617
Ubuntu:24.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2024-56617
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2024-56617
Ubuntu:24.04:LTSlinux-gcp-6.116.11.0-1011.11~24.04.1UBUNTU-CVE-2024-56617
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2024-56617
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2024-56617
Ubuntu:22.04:LTSlinux-gcp-6.8no fix listedUBUNTU-CVE-2024-56617
Ubuntu:24.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2024-56617
Ubuntu:24.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2024-56617
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2024-56617
Ubuntu:24.04:LTSlinux-hwe-6.116.11.0-21.21~24.04.1UBUNTU-CVE-2024-56617
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2024-56617
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2024-56617
Ubuntu:22.04:LTSlinux-hwe-6.8no fix listedUBUNTU-CVE-2024-56617
Ubuntu:24.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2024-56617
Ubuntu:22.04:LTSlinux-ibm-6.8no fix listedUBUNTU-CVE-2024-56617
Ubuntu:24.04:LTSlinux-intelno fix listedUBUNTU-CVE-2024-56617
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2024-56617
Ubuntu:24.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2024-56617
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2024-56617
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2024-56617
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2024-56617
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.8no fix listedUBUNTU-CVE-2024-56617
Ubuntu:24.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2024-56617
Ubuntu:24.04:LTSlinux-nvidia-6.116.11.0-1007.7UBUNTU-CVE-2024-56617
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2024-56617
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2024-56617
Ubuntu:22.04:LTSlinux-nvidia-6.8no fix listedUBUNTU-CVE-2024-56617
Ubuntu:24.04:LTSlinux-nvidia-lowlatencyno fix listedUBUNTU-CVE-2024-56617
Ubuntu:24.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2024-56617
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2024-56617
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2024-56617
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2024-56617
Ubuntu:24.04:LTSlinux-oem-6.116.11.0-1017.17UBUNTU-CVE-2024-56617
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2024-56617
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2024-56617
Ubuntu:24.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2024-56617
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2024-56617
Ubuntu:22.04:LTSlinux-oracle-6.8no fix listedUBUNTU-CVE-2024-56617
Ubuntu:24.04:LTSlinux-raspino fix listedUBUNTU-CVE-2024-56617
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2024-56617
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2024-56617
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2024-56617
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2024-56617
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2024-56617
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2024-56617
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2024-56617
Ubuntu:22.04:LTSlinux-riscv-6.8no fix listedUBUNTU-CVE-2024-56617
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2024-56617
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2024-56617
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2024-56617
Ubuntu:24.04:LTSlinux-vmwareno fix listedUBUNTU-CVE-2024-56617
Ubuntu:24.04:LTSlinux-xilinxno fix listedUBUNTU-CVE-2024-56617

Affected products (as reported)

VendorProductVersions
Linux Linux 6539cffa94957241c096099a57d05fa4d8c7db8a – before 23b5908b11b77ff8d7b8f7b8f11cbab2e1f4bfc26539cffa94957241c096099a57d05fa4d8c7db8a – before 95e197354e0de07e9a20819bdae6562e4dda0f206539cffa94957241c096099a57d05fa4d8c7db8a – before b3fce429a1e030b50c1c91351d69b8667eef627b
Linux Linux 6.4

Weakness: CWE-476 · Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

References