Kernel memory corruption via stale perf group state
Published Jul 29, 2026 · Updated Jul 29, 2026
Memory corruption in Linux Kernel 5.13 allows local users to corrupt PMU context lists through perf event group teardown. perf_event_remove_on_exec() detaches an active group leader with DETACH_EXIT but leaves surviving siblings linked to the removed leader, allowing merge_sched_in() to add an already-linked active_list entry. A local user must create a mixed remove_on_exec group, execute the teardown sequence, close the leader, and reschedule it; the double-add allows compromise of kernel confidentiality, integrity, and availability.
Summary
What happened
Memory corruption in Linux Kernel 5.13 allows local users to corrupt PMU context lists through perf event group teardown. perf_event_remove_on_exec() detaches an active group leader with DETACH_EXIT but leaves surviving siblings linked to the removed leader, allowing merge_sched_in() to add an already-linked active_list entry. A local user must create a mixed remove_on_exec group, execute the teardown sequence, close the leader, and reschedule it; the double-add allows compromise of kernel confidentiality, integrity, and availability.
The record
- CVE
- CVE-2026-64556
- Published
- Jul 29, 2026
- Updated
- Jul 29, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 29, 2026CVE publishedPublication date reported by the CVE source.
- Jul 29, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2e498d0a74e5b88a6689ae1b811f247f91ff188e <037a3c43edfb597665dd34457cd22b14692f2ba3
- Affected versionversion=2e498d0a74e5b88a6689ae1b811f247f91ff188e <06ccef0434e98058ddae7bcebc901f93d22b7653
- Affected versionversion=2e498d0a74e5b88a6689ae1b811f247f91ff188e <39358e856fb89e62e3c8d7389a2dc4ec33dbe90e
- Affected versionversion=2e498d0a74e5b88a6689ae1b811f247f91ff188e <4cdb1b3ab96eb1b7eb70bc5c82fede334bd60df2
- Affected versionversion=2e498d0a74e5b88a6689ae1b811f247f91ff188e <a2d5d3ee7b6e3953114726b1521e62123ab5b043
- Affected versionversion=5.13
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo