GHSA-83QV-JR76-P4XC
Vulnerability from github – Published: 2026-10-28 12:31 – Updated: 2026-10-28 12:31In the Linux kernel, the following vulnerability has been resolved:
s390/pai: Handle multiple PMU stop callback invocations
Handle the following scenario: The kernel protects itself against a very high sampling load and throttles the sampling using:
perf_event_throttle() --> PMU->stop()
Shortly later the scheduler may terminate the task and removes it from the CPU. It again calls
PMU->stop()
which results in two invocations of PMU->stop() called back to back. Protect against this and check the PERF_HES_STOPPED bit on function entry. If it is already set return. Clear bit PERF_HES_STOPPED in PMU->start().
Prohibit ioctl(fd, PERF_EVENT_IOC_PERIOD, ...) call for this event. It sets perf_event::event_limit to a positive value and causes perf_event_overflow() to invoke pai_stop() call back function when perf_event::event_limit hits zero. This is not supported because the sample events CRYPTO_ALL and NNPA_ALL are only taken at schedule out of a task.
Use list_for_each_entry_safe() for safe iteration over syswide_list in pai_have_samples().
{
"affected": [],
"aliases": [
"CVE-2026-99125"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-28T11:17:32Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\ns390/pai: Handle multiple PMU stop callback invocations\n\nHandle the following scenario:\nThe kernel protects itself against a very high sampling load and\nthrottles the sampling using:\n\n perf_event_throttle() --\u003e PMU-\u003estop()\n\nShortly later the scheduler may terminate the task and removes it from the\nCPU. It again calls\n\n PMU-\u003estop()\n\nwhich results in two invocations of PMU-\u003estop() called back to back.\nProtect against this and check the PERF_HES_STOPPED bit on function\nentry. If it is already set return.\nClear bit PERF_HES_STOPPED in PMU-\u003estart().\n\nProhibit ioctl(fd, PERF_EVENT_IOC_PERIOD, ...) call for this event.\nIt sets perf_event::event_limit to a positive value and causes\nperf_event_overflow() to invoke pai_stop() call back function when\nperf_event::event_limit hits zero. This is not supported because the\nsample events CRYPTO_ALL and NNPA_ALL are only taken at schedule out\nof a task.\n\nUse list_for_each_entry_safe() for safe iteration over syswide_list\nin pai_have_samples().",
"id": "GHSA-83qv-jr76-p4xc",
"modified": "2026-10-28T12:31:04Z",
"published": "2026-10-28T12:31:04Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-99125"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/cf348ec613f75b9774291e47b804fd7010835a6c"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/f3110e969ad226ffbb2d9b4bf5387e68d0d9ef40"
}
],
"schema_version": "1.4.0",
"severity": []
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
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.