Description
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.
Published: 2026-08-15
Score: n/a
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The Linux kernel on arm64 fails to validate CPU presence during hotplug, causing a null kobject warning when cpuhp_smt_enable() processes CPUs marked present but not yet registered. This results in sysfs warnings and may disrupt normal boot or lead to instability. While there is no direct evidence of code execution, the inconsistency can cause service interruption or a denial of service under misconfigured conditions.

Affected Systems

All arm64 Linux kernel users that boot with ACPI support and specify a maxcpus count higher than the number of physically present CPUs are potentially affected. The issue arises from smp_prepare_cpus marking every enumerated CPU as present regardless of the MADT flags, leading to unregistered CPUs appearing in the present mask. The vulnerability applies to any distribution using a kernel that does not include the recent patch, independent of vendor.

Risk and Exploitability

No CVSS score is provided and the EPSS metric is unavailable, so the exact exploitation probability is uncertain. The vulnerability is not listed in CISA KEV, indicating no known widespread exploitation. The attack vector is local and would require an attacker to control kernel boot parameters or modify the kernel image. Given these constraints, the risk is low to moderate, with the primary danger being a potential denial of service via repeated sysfs errors.

Generated by OpenCVE AI on August 15, 2026 at 07:39 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Update the kernel to a release that includes the cpuhp_smt_enable null pointer fix (commit 901a489d89ee9c854624c8444090e38e70aed234 or later).
  • Ensure that the maxcpus configuration on arm64 with ACPI does not exceed the number of physically present CPUs; avoid using '-smp maxcpus=N' where N is greater than the real CPU count.
  • If upgrading the kernel is not immediately possible, manually apply the patch from the provided Git commit or disable SMT hotplug via kernel configuration.
  • Continuously monitor dmesg or system logs for repeated "WARNING: fs/sysfs/group.c" entries; persistence of these warnings indicates the vulnerability remains active.

Generated by OpenCVE AI on August 15, 2026 at 07:39 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sat, 15 Aug 2026 08:00:00 +0000

Type Values Removed Values Added
Weaknesses CWE-476

Sat, 15 Aug 2026 06:00:00 +0000

Type Values Removed Values Added
Description 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.
Title cpu/hotplug: Fix NULL kobject warning in cpuhp_smt_enable()
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References

Subscriptions

Linux Linux Kernel
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published:

Updated: 2026-08-15T05:51:44.050Z

Reserved: 2026-08-09T03:40:39.900Z

Link: CVE-2026-72016

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-15T06:21:00.433

Modified: 2026-08-15T06:21:00.433

Link: CVE-2026-72016

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-15T07:45:04Z

Weaknesses