PT-2026-90176 · Linux · Linux

CVE-2026-89460

·

Published

2026-09-11

·

Updated

2026-09-11

None

No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
In the Linux kernel, the following vulnerability has been resolved:
s390/cpum cf: Handle CPU hotplug via prepare/dead callbacks
The command 'perf stat -e cycles -- ' crashes the kernel when CPUs are hotplug added during that run.
Root cause is the allocation of struct cpu cf events at first event initialization. The allocation is dynamic and the first event that has task context creates such a structure for each online CPU. This is not sufficient. CPUs may be offline during event creation and can be set online during the perf run time. For example commands

echo 0 > /sys/devices/system/cpu/cpu1/online

perf stat -e cycles -i -- stress-ng -t10s --matrix X

sleep 1

echo 1 > /sys/devices/system/cpu/cpu1/online

create an event for CPUs 0,2-X. Since the events are created with task-context, the scheduler will eventually schedule the program on CPU1. This CPU has not created and initialized any per CPU event infrastructure as that CPU was not online at the time of the perf invocation. Thus when the scheduler runs stress-ng on CPU1, the function cpumf pmu add() refers to a NULL pointer:
struct cpu cf events *cpuhw = this cpu cfhw();
This function call is invoked after the task stress-ng has been made runnable on CPU1. And this cpu cfhw() returns NULL.
The result is a panic: Unable to handle kernel pointer dereference in virtual kernel address space Failing address: 0000000000000000 TEID: 0000000000000483 .... Krnl PSW : 0404d00180000000 000003ef8291fd0c (cpumf pmu add+0x3c/0x80) .... Call Trace: [<000003ef8291fd0c>] cpumf pmu add+0x3c/0x80 [<000003ef82bb5e3e>] event sched in+0xae/0x190 [<000003ef82bb60d6>] merge sched in+0x1b6/0x390 [<000003ef82bb65b8>] visit groups merge.constprop.0.isra.0+0x308/0x5b0 [<000003ef82bb689a>] pmu groups sched in+0x3a/0x50 [<000003ef82bb6a30>] ctx sched in+0x180/0x260 [<000003ef82bb780c>] perf event context sched in+0x11c/0x2d0 [<000003ef82bb79ee>] perf event task sched in+0x2e/0xc0 [<000003ef82994834>] finish task switch.isra.0+0x1a4/0x250 .... Last Breaking-Event-Address: [<000003ef8291f1d8>] this cpu cfhw+0x38/0x40
The issue arises only in per-task context when the CPUMF facility is used and the scheduler picks a random CPU for such a process to run on. The scheduler enables the CPUMF infrastructure via PMU callback functions pmu::add() and pmu::del().
Introduce a CPU hotplug prepare/dead callback pair which creates and removes the per CPU counter data while the CPU is offline. Count the users which track every CPU (cpu == -1), that is perf event open() events with task context and /dev/hwctr device sessions, in the new counter cpu cf root::tskcnt, protected by pmc reserve mutex. This ensures the infrastructure is available when new CPU is selected to run the per-task context process.
In cpum cf free root() and cpum cf free cpu() ensure the reference pointer to data structures is set to NULL before the data is freed to prevent interrupt handlers to access stale data.
[gor@linux.ibm.com: change commit message]
Found an issue in the description? Have something to add? Feel free to write us 👾

Related Identifiers

CVE-2026-89460

Affected Products

Linux