perf: Fix perf_pmu_migrate_context() leaving events behind
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 3caf006eb731e88cbb33fb5b7d1f2fdb23712bc7, Kernel 3eb08f09bfb364051f51316da873c3bd51a839ef, Kernel d4002e954c612dfc7e3fb5549e4a188ea281fe35 and 2 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.2, >=bd27568117664b8b3e259721393df420ed51f57b <3caf006eb731e88cbb33fb5b7d1f2fdb23712bc7, >=bd27568117664b8b3e259721393df420ed51f57b <3eb08f09bfb364051f51316da873c3bd51a839ef, >=bd27568117664b8b3e259721393df420ed51f57b <d4002e954c612dfc7e3fb5549e4a188ea281fe35, >=bd27568117664b8b3e259721393df420ed51f57b <e76b36b4be7160eaa14b416681e548b125702395, >=bd27568117664b8b3e259721393df420ed51f57b <f5f0028764de322a3d04eda0d3b6389ca9847446 | 3caf006eb731e88cbb33fb5b7d1f2fdb23712bc7, 3eb08f09bfb364051f51316da873c3bd51a839ef, d4002e954c612dfc7e3fb5549e4a188ea281fe35, e76b36b4be7160eaa14b416681e548b125702395, f5f0028764de322a3d04eda0d3b6389ca9847446 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket