# CVE-2026-90123: irqchip/ast2700-intc: Avoid allocating in the irq_domain activate() callback

> A kernel bug in the AST2700 interrupt controller causes a crash when allocating memory with interrupts disabled, leading to local denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-j4hm-9pmg-gfwx, UBUNTU-CVE-2026-90123

## What is CVE-2026-90123?

CVE-2026-90123 is a denial of service vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In 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.

## Which versions are affected by CVE-2026-90123?


## How do I fix CVE-2026-90123?

Apply the vendor's patch.

## Is CVE-2026-90123 being exploited?

There is no known exploitation of CVE-2026-90123 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-90123 and fix it if it is affected.

What it is: CVE-2026-90123 is a denial of service vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-90123 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-90123/ (Markdown: https://insights.sbomify.com/CVE-2026-90123/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-90123
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-90123
- OSV: https://osv.dev/vulnerability/CVE-2026-90123

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-90123/
Summaries are generated and may contain mistakes; the official description above is the record.