Bug 2524434 (CVE-2026-74753) - CVE-2026-74753 kernel: perf: Reject exited events as group leaders
Summary: CVE-2026-74753 kernel: perf: Reject exited events as group leaders
Keywords:
Status: NEW
Alias: CVE-2026-74753
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-08-26 14:51 UTC by OSIDB Bzimport
Modified: 2026-10-05 07:57 UTC (History)
18 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2026:72467 0 None None None 2026-09-28 11:13:23 UTC
Red Hat Product Errata RHSA-2026:72468 0 None None None 2026-09-28 12:03:39 UTC
Red Hat Product Errata RHSA-2026:72623 0 None None None 2026-09-28 18:43:51 UTC
Red Hat Product Errata RHSA-2026:72624 0 None None None 2026-09-28 17:45:11 UTC

Description OSIDB Bzimport 2026-08-26 14:51:29 UTC
In the Linux kernel, the following vulnerability has been resolved:

perf: Reject exited events as group leaders

perf_event_remove_on_exec() sets remove-on-exec events to the EXIT state
and detaches their group relationships.  The event's file descriptor can
remain open, however, and perf_event_open() currently accepts that event
as a group leader because its early validation rejects only REVOKED and
DEAD events.

A new sibling can consequently be linked to the detached leader.  When
the leader is closed, perf_group_detach() observes that its
PERF_ATTACH_GROUP bit is already clear and skips the new sibling.  The
sibling then retains a group_leader pointer to the freed event.

Reject group leaders in the EXIT state.  Perform the check while holding
the shared context mutex so that an exec in the target task cannot detach
the leader between validation and group attachment.

[peterz: make the earlier test fully consistent]

Comment 3 Akiyoshi Kurita 2026-08-28 01:34:48 UTC
FYI, a public exploit / PoC for CVE-2026-74753 is now available.

Red Hat CVE:
https://access.redhat.com/security/cve/cve-2026-74753

Public exploit / PoC:
https://github.com/google/security-research/tree/2623550a891f51ba099fd3cec8f07c32d7e2fc61/pocs/linux/kernelctf/CVE-2026-74753_lts/exploit/lts-6.12.101

Upstream fix:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=fa091f46c3833fb22384f10eade2b4e1e1d0b278

The upstream CVE announcement currently does not list fixed 6.6 or 6.12 stable backports.

From reviewing the upstream fix, I could not identify an obvious practical runtime mitigation other than applying a kernel containing the fix.

Sharing this because a working public exploit is now available.

Comment 7 Jon Orris 2026-09-28 11:13:21 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:72467 https://access.redhat.com/errata/RHSA-2026:72467

Comment 8 Jon Orris 2026-09-28 12:03:38 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:72468 https://access.redhat.com/errata/RHSA-2026:72468

Comment 9 Jon Orris 2026-09-28 17:45:10 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2026:72624 https://access.redhat.com/errata/RHSA-2026:72624

Comment 10 Jon Orris 2026-09-28 18:43:49 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 9

Via RHSA-2026:72623 https://access.redhat.com/errata/RHSA-2026:72623


Note You need to log in before you can comment on or make changes to this bug.