Linux Kernel up to 7.2-rc1 perf/core perf_event_remove_on_exec memory corruption

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
9.5$5k-$25k3.10

Summaryinfo

A vulnerability has been found in Linux Kernel up to 6.6.144/6.12.95/6.18.38/7.1.3/7.2-rc1 and classified as very critical. The affected element is the function perf_event_remove_on_exec of the component perf/core. Performing a manipulation results in memory corruption. This vulnerability was named CVE-2026-64556. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability classified as very critical has been found in Linux Kernel up to 6.6.144/6.12.95/6.18.38/7.1.3/7.2-rc1. This affects the function perf_event_remove_on_exec of the component perf/core. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

In the Linux kernel, the following vulnerability has been resolved: perf/core: Detach event groups during remove_on_exec perf_event_remove_on_exec() removes events by calling perf_event_exit_event(). For top-level events, this removes the event from the context with DETACH_EXIT only. This can leave inconsistent group state when a removed event is a group leader and the group contains siblings without remove_on_exec. If the group was active, the surviving siblings can remain active and attached to the removed leader's sibling list, but are no longer represented by a valid group leader on the PMU context active lists. A later close of the removed leader uses DETACH_GROUP and can promote the still-active siblings from this stale group state. The next schedule-in can then add an already-linked active_list entry again, corrupting the PMU context active list. With DEBUG_LIST enabled, this is caught as a list_add double-add in merge_sched_in(). Fix this by detaching group relationships when remove_on_exec removes an event. This preserves the existing task-exit and revoke behavior, while ensuring surviving siblings are ungrouped before the removed event leaves the context.

The advisory is shared at git.kernel.org. This vulnerability is uniquely identified as CVE-2026-64556 since 07/19/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details are known, but no exploit is available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 07/29/2026).

Upgrading to version 6.6.145, 6.12.96, 6.18.39, 7.1.4 or 7.2-rc2 eliminates this vulnerability. Applying the patch 4cdb1b3ab96eb1b7eb70bc5c82fede334bd60df2/39358e856fb89e62e3c8d7389a2dc4ec33dbe90e/a2d5d3ee7b6e3953114726b1521e62123ab5b043/06ccef0434e98058ddae7bcebc901f93d22b7653/037a3c43edfb597665dd34457cd22b14692f2ba3 is able to eliminate this problem.

The vulnerability is also documented in the databases at EUVD (EUVD-2026-50201) and CERT Bund (WID-SEC-2026-2570). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Affected

  • Open Source Linux Kernel

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 9.9
VulDB Meta Temp Score: 9.5

VulDB Base Score: 9.9
VulDB Temp Score: 9.5
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Memory corruption
CWE: CWE-119
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 6.6.145/6.12.96/6.18.39/7.1.4/7.2-rc2
Patch: 4cdb1b3ab96eb1b7eb70bc5c82fede334bd60df2/39358e856fb89e62e3c8d7389a2dc4ec33dbe90e/a2d5d3ee7b6e3953114726b1521e62123ab5b043/06ccef0434e98058ddae7bcebc901f93d22b7653/037a3c43edfb597665dd34457cd22b14692f2ba3

Timelineinfo

07/19/2026 CVE reserved
07/29/2026 +10 days Advisory disclosed
07/29/2026 +0 days VulDB entry created
07/29/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-64556 (🔒)
GCVE (CVE): GCVE-0-2026-64556
GCVE (VulDB): GCVE-100-384093
EUVD: 🔒
CERT Bund: WID-SEC-2026-2570 - Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

Entryinfo

Created: 07/29/2026 10:41
Updated: 07/29/2026 14:34
Changes: 07/29/2026 10:41 (59), 07/29/2026 12:48 (1), 07/29/2026 14:34 (7)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you want to use VulDB in your project?

Use the official API to access entries easily!