GHSA-47G9-QXGV-4Q29
Vulnerability from github – Published: 2026-10-06 09:31 – Updated: 2026-10-06 09:31In the Linux kernel, the following vulnerability has been resolved:
perf: Fix null pointer access in is_include_guest_event()
A typical module unload occurring event when there is an active perf connection leads to freeing of the pmu pointer. The call log is something like: .. __pmu_detach_event pmu_detach_event pmu_detach_events perf_pmu_unregister ..
__pmu_detach_event() sets event->pmu to null. When the perf connection finally is closed, the following stack trace is observed:
Oops: general protection fault, kernel NULL pointer dereference ... RIP: 0010:_free_event+0x3e/0x370 ... Call Trace: ... perf_event_release_kernel+0x260/0x2d0 perf_release+0x12/0x20
A call to mediated_pmu_unaccount_event() inside _free_event() is the root cause of this crash. Adding a check inside is_include_guest_event() ensures we don't accidentally access a null pmu ptr. In addition to this, we will now call mediated_pmu_unaccount_event() before clearing the pmu ptr so that nr_include_guest_events counts are maintained correctly.
{
"affected": [],
"aliases": [
"CVE-2026-98268"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-06T09:18:16Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nperf: Fix null pointer access in is_include_guest_event()\n\nA typical module unload occurring event when there is an active perf\nconnection leads to freeing of the pmu pointer. The call log is something\nlike:\n ..\n __pmu_detach_event\n pmu_detach_event\n pmu_detach_events\n perf_pmu_unregister\n ..\n\n__pmu_detach_event() sets event-\u003epmu to null. When the perf connection\nfinally is closed, the following stack trace is observed:\n\n Oops: general protection fault, kernel NULL pointer dereference\n ...\n RIP: 0010:_free_event+0x3e/0x370\n ...\n Call Trace:\n ...\n perf_event_release_kernel+0x260/0x2d0\n perf_release+0x12/0x20\n\nA call to mediated_pmu_unaccount_event() inside _free_event() is the root\ncause of this crash. Adding a check inside is_include_guest_event() ensures\nwe don\u0027t accidentally access a null pmu ptr. In addition to this, we will\nnow call mediated_pmu_unaccount_event() before clearing the pmu ptr so that\nnr_include_guest_events counts are maintained correctly.",
"id": "GHSA-47g9-qxgv-4q29",
"modified": "2026-10-06T09:31:32Z",
"published": "2026-10-06T09:31:32Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98268"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/7fa9a465ae8f07c0e4685db6edb6a6f984dbd784"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/88aed0422f39b22406f35f1e758cea25e7bbcfb5"
}
],
"schema_version": "1.4.0",
"severity": []
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.