Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 32 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (15 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 3fed09559cd8be79568d368ce02bf7f2d56259b6 – < c043591f03a8111f7d306b8122c444a949486269
    • affected 3fed09559cd8be79568d368ce02bf7f2d56259b6 – < b5ba8b861b5d833394bd23df3f4b59883ef18c88
    • affected 3fed09559cd8be79568d368ce02bf7f2d56259b6 – < 3791e242ec2e5a5cd9e010a75ed1125d0e84d394
    • affected 3fed09559cd8be79568d368ce02bf7f2d56259b6 – < 38c6831fefde0ff89f8d2dcb924f957a89dec414
    • affected 3fed09559cd8be79568d368ce02bf7f2d56259b6 – < dbecbe23dc606c4af68b4591a41124186f5c1802
    • affected 3fed09559cd8be79568d368ce02bf7f2d56259b6 – < 50b10bd0c2d721ad38abd1abe3acdefb6caa0944
  • Linux · Linux

    • affected 6.0
    • unaffected < 6.0
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-90124 badge
[![CVE-2026-90124](https://cveledger.app/badge/CVE-2026-90124.svg)](https://cveledger.app/cve/CVE-2026-90124)

Record last updated .