GHSA-3XGC-Q8GM-M2RG
Vulnerability from github – Published: 2026-09-17 18:32 – Updated: 2026-09-17 18:32In the Linux kernel, the following vulnerability has been resolved:
sched_ext: Abort directly from the hardlockup handler
scx_hardlockup() defers the abort to an irq_work because exit claiming used to take scx_sched_lock and couldn't run from NMI. The deferral is now unnecessary - claiming is NMI-safe and asserting ->aborting is exactly what breaks the live-locks that hard-lock CPUs. Call handle_lockup() directly and drop the irq_work. This also makes the self-detected case recoverable: the perf watchdog fires on the hard-locked CPU itself, where a queued irq_work never runs with IRQs off.
Also fix the return value: %true used to be returned whenever sched_ext was loaded, suppressing the kernel's hardlockup report even when the abort was refused. Return %true only when this call initiated the abort.
{
"affected": [],
"aliases": [
"CVE-2026-90432"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-17T17:17:48Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nsched_ext: Abort directly from the hardlockup handler\n\nscx_hardlockup() defers the abort to an irq_work because exit claiming used\nto take scx_sched_lock and couldn\u0027t run from NMI. The deferral is now\nunnecessary - claiming is NMI-safe and asserting -\u003eaborting is exactly what\nbreaks the live-locks that hard-lock CPUs. Call handle_lockup() directly and\ndrop the irq_work. This also makes the self-detected case recoverable: the\nperf watchdog fires on the hard-locked CPU itself, where a queued irq_work\nnever runs with IRQs off.\n\nAlso fix the return value: %true used to be returned whenever sched_ext was\nloaded, suppressing the kernel\u0027s hardlockup report even when the abort was\nrefused. Return %true only when this call initiated the abort.",
"id": "GHSA-3xgc-q8gm-m2rg",
"modified": "2026-09-17T18:32:05Z",
"published": "2026-09-17T18:32:05Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-90432"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/3c4b38064937a761ebbf85b1649e812db85eb59e"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/4d6270bbb4e083a4d2d39f3c36f30f5c939c06ed"
}
],
"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.
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.