VulnerabilityPublished 28 Oct 2026

CVE-2026-99187: Linux kernel · perf: Fix perf_pmu_migrate_context() leaving events behind

Affects Linux kernelSource CVE Database V5

Not known to be exploited · fixed in f5f0028764de322a3d04eda0d3b6389ca9847446 : update Linux kernel when convenient.

Data as of 28 Oct 2026, 10:58 UTC

Severity

Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Patch: Available – fixed in f5f0028764de322a3d04eda0d3b6389ca9847446, e76b36b4be7160eaa14b416681e548b125702395, 3eb08f09bfb364051f51316da873c3bd51a839ef

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Linux kernel to f5f0028764de322a3d04eda0d3b6389ca9847446, e76b36b4be7160eaa14b416681e548b125702395 or 3eb08f09bfb364051f51316da873c3bd51a839ef.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ bd27568117664b8b3e259721393df420ed51f57b, < f5f0028764de322a3d04eda0d3b6389ca9847446	Fixed in f5f0028764de322a3d04eda0d3b6389ca9847446
LinuxLinux	Affected ≥ bd27568117664b8b3e259721393df420ed51f57b, < e76b36b4be7160eaa14b416681e548b125702395	Fixed in e76b36b4be7160eaa14b416681e548b125702395
LinuxLinux	Affected ≥ bd27568117664b8b3e259721393df420ed51f57b, < 3eb08f09bfb364051f51316da873c3bd51a839ef	Fixed in 3eb08f09bfb364051f51316da873c3bd51a839ef
LinuxLinux	Affected =6.2	Fixed in–

Description

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.

References

Community reviews

Loading reviews…