Linux kernel event cleanup failure in perf CPU hotplug
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s perf PMU context migration can leave event groups on the source CPU during CPU hotplug. Those events keep running until that CPU is torn down, while the PMU interrupt and migrated events are on another CPU. The input does not specify how an attacker could trigger this or whether access or user interaction is required.
Engineers running the Linux kernel should check their versions; affected versions are not specified.