GHSA-J4HM-9PMG-GFWX
Vulnerability from github – Published: 2026-09-17 18:31 – Updated: 2026-09-17 18:31In the Linux kernel, the following vulnerability has been resolved:
irqchip/ast2700-intc: Avoid allocating in the irq_domain activate() callback
The interrupt core calls the irq_domain_activate() callback from __setup_irq() with desc->lock held and interrupts disabled. Both aspeed_intc1_irq_domain_activate() and aspeed_intc0_resolve_route() test a compatible string with fwnode_device_is_compatible().
fwnode_device_is_compatible() invokes fwnode_property_match_string(), which allocates with GFP_KERNEL. That's obviously not possible with interrupts disabled and a raw spinlock held.
Both call sites are only ever handed OF nodes, so use of_device_is_compatible() instead: it walks the property in place and does not allocate.
{
"affected": [],
"aliases": [
"CVE-2026-90123"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-17T17:17:04Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nirqchip/ast2700-intc: Avoid allocating in the irq_domain activate() callback\n\nThe interrupt core calls the irq_domain_activate() callback from\n__setup_irq() with desc-\u003elock held and interrupts disabled. Both\naspeed_intc1_irq_domain_activate() and aspeed_intc0_resolve_route() test a\ncompatible string with fwnode_device_is_compatible().\n\nfwnode_device_is_compatible() invokes fwnode_property_match_string(), which\nallocates with GFP_KERNEL. That\u0027s obviously not possible with interrupts\ndisabled and a raw spinlock held.\n\nBoth call sites are only ever handed OF nodes, so use\nof_device_is_compatible() instead: it walks the property in place and does\nnot allocate.",
"id": "GHSA-j4hm-9pmg-gfwx",
"modified": "2026-09-17T18:31:51Z",
"published": "2026-09-17T18:31:51Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-90123"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/b76eee9c2157223aa4aac42ceebb563288e078aa"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/f2f0da11648616e47419dca93610f6c0d70ec00b"
}
],
"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.