Interrupt loss via racy status-register clearing
Published Sep 17, 2026 · Updated Sep 17, 2026
An interrupt race in Renesas RZ/G2L support in Linux 6.0 allows local users to discard interrupts through simultaneous GPIO events. The rzg2l_clear_irq_int() and rzg2l_clear_tint_int() functions read-modify-write the write-0-to-clear ISCR/TSCR registers, accidentally clearing another interrupt that arrives between the read and write. Triggering requires access to GPIOs on affected hardware and concurrent interrupts; the documented consequence is lost interrupt delivery, not a demonstrated crash or reboot.
Summary
What happened
An interrupt race in Renesas RZ/G2L support in Linux 6.0 allows local users to discard interrupts through simultaneous GPIO events. The rzg2l_clear_irq_int() and rzg2l_clear_tint_int() functions read-modify-write the write-0-to-clear ISCR/TSCR registers, accidentally clearing another interrupt that arrives between the read and write. Triggering requires access to GPIOs on affected hardware and concurrent interrupts; the documented consequence is lost interrupt delivery, not a demonstrated crash or reboot.
The record
- CVE
- CVE-2026-90124
- Published
- Sep 17, 2026
- Updated
- Sep 17, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 17, 2026CVE publishedPublication date reported by the CVE source.
- Sep 17, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3fed09559cd8be79568d368ce02bf7f2d56259b6 <3791e242ec2e5a5cd9e010a75ed1125d0e84d394
- Affected versionversion=3fed09559cd8be79568d368ce02bf7f2d56259b6 <38c6831fefde0ff89f8d2dcb924f957a89dec414
- Affected versionversion=3fed09559cd8be79568d368ce02bf7f2d56259b6 <50b10bd0c2d721ad38abd1abe3acdefb6caa0944
- Affected versionversion=3fed09559cd8be79568d368ce02bf7f2d56259b6 <b5ba8b861b5d833394bd23df3f4b59883ef18c88
- Affected versionversion=3fed09559cd8be79568d368ce02bf7f2d56259b6 <c043591f03a8111f7d306b8122c444a949486269
- Affected versionversion=3fed09559cd8be79568d368ce02bf7f2d56259b6 <dbecbe23dc606c4af68b4591a41124186f5c1802
- Affected versionversion=6.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
- Concurrent GPIO interrupt-loss reproducerproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started