Menu

Star on GitHub · 3.2k

CVE-2026-72016

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 pr…

Published Aug 15, 2026EPSS 0.21%

Overview

CVE-2026-72016 is a known-severity vulnerability. It was published on August 15, 2026.

Technical 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

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-72016?

CVE-2026-72016 is a known-severity vulnerability. It was published on August 15, 2026.

How severe is CVE-2026-72016?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2026-72016?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-72016?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-72016 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.