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-23287irqchip/sifive-plic: Fix frozen interrupt due to affinity setting

Description

In the Linux kernel, the following vulnerability has been resolved: irqchip/sifive-plic: Fix frozen interrupt due to affinity setting PLIC ignores interrupt completion message for disabled interrupt, explained by the specification: The PLIC signals it has completed executing an interrupt handler by writing the interrupt ID it received from the claim to the claim/complete register. The PLIC does not check whether the completion ID is the same as the last claim ID for that target. If the completion ID does not match an interrupt source that is currently enabled for the target, the completion is silently ignored. This caused problems in the past, because an interrupt can be disabled while still being handled and plic_irq_eoi() had no effect. That was fixed by checking if the interrupt is disabled, and if so enable it, before sending the completion message. That check is done with irqd_irq_disabled(). However, that is not sufficient because the enable bit for the handling hart can be zero despite irqd_irq_disabled(d) being false. This can happen when affinity setting is changed while a hart is still handling the interrupt. This problem is easily reproducible by dumping a large file to uart (which generates lots of interrupts) and at the same time keep changing the uart interrupt's affinity setting. The uart port becomes frozen almost instantaneously. Fix this by checking PLIC's enable bit instead of irqd_irq_disabled().

Timeline

  1. ID reserved

    By Linux

  2. · 2 months later

    Published

  3. · 8 months 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

CVSS scores of CVE-2026-23287, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.13% · top 97% of all CVEs (17 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected cc9f04f9a84f745949e325661550ed14bd0ff322 – < 8942fb1a5bc2dcbd88f7e656d109d42f778f298f
    • affected cc9f04f9a84f745949e325661550ed14bd0ff322 – < 2edbd173309165d103be6c73bd83e459dc45ae7b
    • affected cc9f04f9a84f745949e325661550ed14bd0ff322 – < 686eb378a4a51aa967e08337dd59daade16aec0f
    • affected cc9f04f9a84f745949e325661550ed14bd0ff322 – < 1883332bf21feb8871af09daf604fc4836a76925
    • affected cc9f04f9a84f745949e325661550ed14bd0ff322 – < f611791a927141d05d7030607dea6372311c1413
    • affected cc9f04f9a84f745949e325661550ed14bd0ff322 – < 1072020685f4b81f6efad3b412cdae0bd62bb043
  • Linux · Linux

    • affected 5.1
    • unaffected < 5.1
    • unaffected 6.1.167 – ≤ 6.1.*
    • unaffected 6.6.130 – ≤ 6.6.*
    • unaffected 6.12.77 – ≤ 6.12.*
    • unaffected 6.18.17 – ≤ 6.18.*
    • unaffected 6.19.7 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References9

Sources

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

Badge for a README or a ticket

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

Record last updated .