VDB

CVE-2026-72016

CVE-2026-72016 PUBLISHED

cpu/hotplug: Fix NULL kobject warning in cpuhp_smt_enable()

Reported by linux · Published August 15, 2026

In the Linux kernel, the following vulnerability has been resolved: cpu/hotplug: Fix NULL kobject warning in cpuhp_smt_enable() On arm64, when booting with `maxcpus` greater than the number of present CPUs (e.g., QEMU -smp cpus=4,maxcpus=8), some CPUs are marked as 'present' but have not yet been registered via register_cpu(). Consequently, the per-cpu device objects for these CPUs are not yet initialized. In cpuhp_smt_enable(), the code iterates over all present CPUs. Calling _cpu_up() for these unregistered CPUs eventually leads to sysfs_create_group() being called with a NULL kobject (or a kobject without a directory), triggering the following warning in fs/sysfs/group.c: WARNING: fs/sysfs/group.c:137 at internal_create_group+0x41c/0x4bc, CPU#2: sh/181 [...] Call trace: internal_create_group+0x41c/0x4bc (P) sysfs_create_group+0x18/0x24 topology_add_dev+0x1c/0x28 cpuhp_invoke_callback+0x104/0x20c __cpuhp_invoke_callback_range+0x94/0x11c _cpu_up+0x200/0x37c When booting with ACPI, arm64 smp_prepare_cpus() currently sets all enumerated CPUs as "present" regardless of their status in the MADT. This causes issues with SMT hotplug control. For instance, with QEMU's "-smp 4,maxcpus=8" configuration, the MADT GICC entries are populated as follows: 1. The first four CPUs: `Enabled` set but `Online Capable` not set. 2. The remaining four CPUs: `Online Capable` set but `Enabled` not set to support potential hot-plugging. Fix this by: 1. When booting with ACPI, checking the ACPI_MADT_ENABLED flag in the GICC entry before calling set_cpu_present() during SMP initialization. 2. Properly managing the present mask in acpi_map_cpu() and acpi_unmap_cpu() to support actual CPU hotplug events, This aligns with other architectures like x86 and LoongArch. 3. Update the arm64 CPU hotplug documentation to no longer state that all online-capable vCPUs are marked as present by the kernel at boot time. This ensures that only physically available or explicitly enabled CPUs are in the present mask, keeping the SMT control logic consistent with the actual hardware state.

EPSS 0.21% · 10.7th percentile

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
kernel6.18-modules-extra-commonAmazon Linux1:6.18.41-94.142.amzn2023
kernel-livepatch-6.18.41-94.142Amazon Linux1:1.0-0.amzn2023
kernel6.18-tools-develAmazon Linux1:6.18.41-94.142.amzn2023
kernel6.18-toolsAmazon Linux1:6.18.41-94.142.amzn2023
kernel6.18-modules-extraAmazon Linux1:6.18.41-94.142.amzn2023
perf6.18Amazon Linux1:6.18.41-94.142.amzn2023
python3-perf6.18Amazon Linux1:6.18.41-94.142.amzn2023
kernel6.18Amazon Linux1:6.18.41-94.142.amzn2023
kernel6.18-headersAmazon Linux1:6.18.41-94.142.amzn2023

Risk scores

EPSS Score
0.21%
10.7th percentile

Affected products

VendorProductVersions
LinuxLinuxeed4583bcf9a60f8d6dd3a3c7c94dea28134b1eb, eed4583bcf9a60f8d6dd3a3c7c94dea28134b1eb, eed4583bcf9a60f8d6dd3a3c7c94dea28134b1eb
LinuxLinux6.15, 0, 6.18.40
amazon:2023kernel6.18-modules-extra-common0
amazon:2023kernel-livepatch-6.18.41-94.1420
amazon:2023kernel6.18-tools-devel0
amazon:2023kernel6.18-tools0
amazon:2023kernel6.18-modules-extra0
amazon:2023perf6.180
amazon:2023python3-perf6.180
amazon:2023kernel6.180
amazon:2023kernel6.18-headers0
linuxlinux_kernel6.15, 6.15, 6.15
amazon:2023bpftool6.180
amazon:2023kernel6.18-devel0
LinuxLinux*, *, *
amazon:2023microvm-kernel6.180

Timeline

  • Aug 15, 2026 Coalition ESS Score
  • Aug 15, 2026 CVE Published
  • Aug 17, 2026 CVE Updated
  • Aug 19, 2026 Security Advisory
  • Aug 24, 2026 EPSS Score (13 in total, the first dated here)

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2026-72016
vulnetix vdb fixes CVE-2026-72016

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-72016/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›