{"id":"CVE-2026-23287","summary":"irqchip/sifive-plic: Fix frozen interrupt due to affinity setting","details":"In the Linux kernel, the following vulnerability has been resolved:\n\nirqchip/sifive-plic: Fix frozen interrupt due to affinity setting\n\nPLIC ignores interrupt completion message for disabled interrupt, explained\nby the specification:\n\n    The PLIC signals it has completed executing an interrupt handler by\n    writing the interrupt ID it received from the claim to the\n    claim/complete register. The PLIC does not check whether the completion\n    ID is the same as the last claim ID for that target. If the completion\n    ID does not match an interrupt source that is currently enabled for\n    the target, the completion is silently ignored.\n\nThis caused problems in the past, because an interrupt can be disabled\nwhile still being handled and plic_irq_eoi() had no effect. That was fixed\nby checking if the interrupt is disabled, and if so enable it, before\nsending the completion message. That check is done with irqd_irq_disabled().\n\nHowever, that is not sufficient because the enable bit for the handling\nhart can be zero despite irqd_irq_disabled(d) being false. This can happen\nwhen affinity setting is changed while a hart is still handling the\ninterrupt.\n\nThis problem is easily reproducible by dumping a large file to uart (which\ngenerates lots of interrupts) and at the same time keep changing the uart\ninterrupt's affinity setting. The uart port becomes frozen almost\ninstantaneously.\n\nFix this by checking PLIC's enable bit instead of irqd_irq_disabled().","modified":"2026-04-14T03:48:10.804243Z","published":"2026-03-25T10:26:46.363Z","database_specific":{"osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/23xxx/CVE-2026-23287.json","cna_assigner":"Linux"},"references":[{"type":"PACKAGE","url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"},{"type":"WEB","url":"https://git.kernel.org/stable/c/1072020685f4b81f6efad3b412cdae0bd62bb043"},{"type":"WEB","url":"https://git.kernel.org/stable/c/1883332bf21feb8871af09daf604fc4836a76925"},{"type":"WEB","url":"https://git.kernel.org/stable/c/2edbd173309165d103be6c73bd83e459dc45ae7b"},{"type":"WEB","url":"https://git.kernel.org/stable/c/686eb378a4a51aa967e08337dd59daade16aec0f"},{"type":"WEB","url":"https://git.kernel.org/stable/c/8942fb1a5bc2dcbd88f7e656d109d42f778f298f"},{"type":"WEB","url":"https://git.kernel.org/stable/c/f611791a927141d05d7030607dea6372311c1413"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/23xxx/CVE-2026-23287.json"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-23287"}],"affected":[{"ranges":[{"type":"GIT","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","events":[{"introduced":"cc9f04f9a84f745949e325661550ed14bd0ff322"},{"fixed":"8942fb1a5bc2dcbd88f7e656d109d42f778f298f"},{"fixed":"2edbd173309165d103be6c73bd83e459dc45ae7b"},{"fixed":"686eb378a4a51aa967e08337dd59daade16aec0f"},{"fixed":"1883332bf21feb8871af09daf604fc4836a76925"},{"fixed":"f611791a927141d05d7030607dea6372311c1413"},{"fixed":"1072020685f4b81f6efad3b412cdae0bd62bb043"}]}],"database_specific":{"source":"https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2026-23287.json"}},{"package":{"name":"Kernel","ecosystem":"Linux"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"5.1.0"},{"fixed":"6.1.167"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.2.0"},{"fixed":"6.6.130"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.7.0"},{"fixed":"6.12.77"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.13.0"},{"fixed":"6.18.17"}]},{"type":"ECOSYSTEM","events":[{"introduced":"6.19.0"},{"fixed":"6.19.7"}]}],"database_specific":{"source":"https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2026-23287.json"}}],"schema_version":"1.7.5"}