Live › vulnerability › CVE-2026-99187
Go to dashboardWhen a CPU is hotplugged, the kernel's perf subsystem can fail to move all of a PMU's performance events to another CPU, leaving some running on the dying CPU. The sources do not describe a direct way for an attacker to gain code execution or data access.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-28 11:32 UTC. All times on this page are UTC.
No product ranges from the sources yet.
Unknown from the sources.
Unknown from the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
In the Linux kernel, the following vulnerability has been resolved:
perf: Fix perf_pmu_migrate_context() leaving events behind
__perf_pmu_remove() walks the group leaders of a CPU and PMU with perf_event_groups_for_cpu_pmu(), removing each one as it goes. perf_remove_from_context() takes the leader out of the groups rbtree, after which rb_next() on that node returns NULL, prematurely ending the walk. Other groups stay behind in the source context.
On CPU hotplug, they are then torn down with the dying CPU. They keep running until teardown, while the PMU's interrupt and migrated events are on a new CPU, which drivers rely on never happening.
Walk ctx->event_list instead and pick out the PMU's events by their pmu_ctx.
This page as .md · .json · in your agent: get_signal("CVE-2026-99187")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.