Home

Description

In the Linux kernel, the following vulnerability has been resolved: perf/core: Fix WARN_ON(!ctx) in __free_event() for partial init Move the get_ctx(child_ctx) call and the child_event->ctx assignment to occur immediately after the child event is allocated. Ensure that child_event->ctx is non-NULL before any subsequent error path within inherit_event calls free_event(), satisfying the assumptions of the cleanup code. Details: There's no clear Fixes tag, because this bug is a side-effect of multiple interacting commits over time (up to 15 years old), not a single regression. The code initially incremented refcount then assigned context immediately after the child_event was created. Later, an early validity check for child_event was added before the refcount/assignment. Even later, a WARN_ON_ONCE() cleanup check was added, assuming event->ctx is valid if the pmu_ctx is valid. The problem is that the WARN_ON_ONCE() could trigger after the initial check passed but before child_event->ctx was assigned, violating its precondition. The solution is to assign child_event->ctx right after its initial validation. This ensures the context exists for any subsequent checks or cleanup routines, resolving the WARN_ON_ONCE(). To resolve it, defer the refcount update and child_event->ctx assignment directly after child_event->pmu_ctx is set but before checking if the parent event is orphaned. The cleanup routine depends on event->pmu_ctx being non-NULL before it verifies event->ctx is non-NULL. This also maintains the author's original intent of passing in child_ctx to find_get_pmu_context before its refcount/assignment. [ mingo: Expanded the changelog from another email by Gabriel Shahrouzi. ]

PUBLISHED Reserved 2025-04-16 | Published 2025-05-09 | Updated 2026-01-02 | Assigner Linux

Product status

Default status
unaffected

7ef5aa081f989ecfecc1df02068a80aebbd3ec31 (git) before 90dc6c1e3b200812da8d0aa030e1b7fda8226d0e
affected

1209b0b29fd472e7dbd2b06544b019dd9f9b7e51 (git) before cb56cd11feabf99e08bc18960700a53322ffcea7
affected

c70ca298036c58a88686ff388d3d367e9d21acf0 (git) before 0ba3a4ab76fd3367b9cb680cad70182c896c795c
affected

315a50c6b1c6ce191f19f3372935d8e2ed9b53a6 (git)
affected

Default status
unaffected

6.12.24 (semver) before 6.12.26
affected

6.14.3 (semver) before 6.14.5
affected

References

git.kernel.org/...c/90dc6c1e3b200812da8d0aa030e1b7fda8226d0e

git.kernel.org/...c/cb56cd11feabf99e08bc18960700a53322ffcea7

git.kernel.org/...c/0ba3a4ab76fd3367b9cb680cad70182c896c795c

cve.org (CVE-2025-37878)

nvd.nist.gov (CVE-2025-37878)

Download JSON