GHSA-XGWF-QW68-FXV2
Vulnerability from github – Published: 2026-09-17 18:31 – Updated: 2026-09-17 18:31In the Linux kernel, the following vulnerability has been resolved:
ARM: 9484/1: enable interrupts when unhandled user faults are triggered
PREEMPT_RT requires interrupts to be enabled when sending signals.
When do_DataAbort()/do_PrefetchAbort() triggers unhandled user faults,
that is inf->fn() return a non-zero value, and the interrupts are not
enabled within the hook function, force_sig_fault() will be called
with interrupts disabled.
This can be triggered by user programs executing the bkpt instruction, with kernel config CONFIG_PERF_EVENTS=n.
Enable interrupts in do_DataAbort()/do_PrefetchAbort() when unhandled user faults are triggered to fix the issue.
{
"affected": [],
"aliases": [
"CVE-2026-90304"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-17T17:17:28Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nARM: 9484/1: enable interrupts when unhandled user faults are triggered\n\nPREEMPT_RT requires interrupts to be enabled when sending signals.\n\nWhen do_DataAbort()/do_PrefetchAbort() triggers unhandled user faults,\nthat is `inf-\u003efn()` return a non-zero value, and the interrupts are not\nenabled within the hook function, force_sig_fault() will be called\nwith interrupts disabled.\n\nThis can be triggered by user programs executing the bkpt instruction,\nwith kernel config CONFIG_PERF_EVENTS=n.\n\nEnable interrupts in do_DataAbort()/do_PrefetchAbort() when unhandled\nuser faults are triggered to fix the issue.",
"id": "GHSA-xgwf-qw68-fxv2",
"modified": "2026-09-17T18:31:59Z",
"published": "2026-09-17T18:31:59Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-90304"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/8d7cbc6df9632d334b21c4be66ccdde76a08fb13"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/e79ca91165d4fd18549c536abdb86101e889052f"
}
],
"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.