# CVE-2026-90124: irqchip/renesas-rzg2l: Fix loss of interrupt

> A race condition in the Renesas RZ/G2L interrupt controller driver can cause loss of interrupts, leading to 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:** AZL-102216, BELL-CVE-2026-90124, DEBIAN-CVE-2026-90124, GHSA-h8c5-9rgx-f76h, UBUNTU-CVE-2026-90124

## What is CVE-2026-90124?

CVE-2026-90124 is a 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/renesas-rzg2l: Fix loss of interrupt

rzg2l_clear_irq_int() and rzg2l_clear_tint_int() perform a
read-modify-write on the ISCR/TSCR status registers to clear the bit
for the interrupt just handled. Since these registers are
write-0-to-clear per bit, this is racy:

If another interrupt's status bit gets set between the read and the write,
that bit is written back as 0 by the software-constructed value, clearing
an interrupt that hasn't been serviced yet and losing it.

This can be reproduced by triggering multiple interrupts at once, e.g.:

  gpioset -c gpiochip0 355=0 353=0 328=0 352=0

Fix this by writing back only the bit being cleared, with all other bits
set to 1, instead of read-modify-writing the whole register.  Since 1-bits
are left unchanged by hardware, concurrently-set status bits for other
interrupts are preserved.

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


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

Apply the vendor's patch.

## Is CVE-2026-90124 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-90124 is a 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-90124 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-90124/ (Markdown: https://insights.sbomify.com/CVE-2026-90124/index.md)
```

## Sources

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

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