CVE-2025-37878

Source
https://cve.org/CVERecord?id=CVE-2025-37878
Import Source
https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2025-37878.json
JSON Data
https://api.test.osv.dev/v1/vulns/CVE-2025-37878
Downstream
AZL (1)
BELL (1)
CLSA (3)
DEBIAN (1)
ECHO (1)
MGASA (2)
MINI (1)
OESA (2)
ROOT (4)
UBUNTU (1)
Published
2025-05-09T06:45:42Z
Modified
2026-11-13T04:03:35Z
Summary
perf/core: Fix WARN_ON(!ctx) in __free_event() for partial init
Details

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. ]

Database specific
{
    "cna_assigner": "Linux",
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/37xxx/CVE-2025-37878.json"
}
References

Affected packages

Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Affected ranges

Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
7ef5aa081f989ecfecc1df02068a80aebbd3ec31
Fixed
90dc6c1e3b200812da8d0aa030e1b7fda8226d0e
Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
1209b0b29fd472e7dbd2b06544b019dd9f9b7e51
Fixed
cb56cd11feabf99e08bc18960700a53322ffcea7
Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
c70ca298036c58a88686ff388d3d367e9d21acf0
Fixed
0ba3a4ab76fd3367b9cb680cad70182c896c795c
Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
315a50c6b1c6ce191f19f3372935d8e2ed9b53a6

Affected versions

v6.*
v6.12.24
v6.12.25
v6.13.12
v6.14.3
v6.14.4

Database specific

source
"https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2025-37878.json"

Linux / Kernel

Package

Name
Kernel

Affected ranges

Type
ECOSYSTEM
Events
Introduced
6.13.12
Fixed
6.14
Type
ECOSYSTEM
Events
Introduced
6.12.24
Fixed
6.12.26
Type
ECOSYSTEM
Events
Introduced
6.14.3
Fixed
6.14.5

Database specific

source
"https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2025-37878.json"