CVE-2026-23470
Received Received - Intake
Deadlock Vulnerability in Linux drm/imagination Soft Reset Sequence

Publication date: 2026-04-03

Last updated on: 2026-04-03

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: drm/imagination: Fix deadlock in soft reset sequence The soft reset sequence is currently executed from the threaded IRQ handler, hence it cannot call disable_irq() which internally waits for IRQ handlers, i.e. itself, to complete. Use disable_irq_nosync() during a soft reset instead.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-04-03
Last Modified
2026-04-03
Generated
2026-05-07
AI Q&A
2026-04-03
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability exists in the Linux kernel's drm/imagination component related to the soft reset sequence.

The issue arises because the soft reset sequence is executed from a threaded IRQ handler, which cannot safely call disable_irq() since disable_irq() waits for IRQ handlers, including itself, to complete, causing a deadlock.

The fix involves using disable_irq_nosync() during the soft reset instead of disable_irq(), preventing the deadlock.


How can this vulnerability impact me? :

This vulnerability can cause a deadlock in the Linux kernel's soft reset sequence for the drm/imagination component.

A deadlock in this context could lead to system instability or a hang during the reset process, potentially affecting system reliability and availability.


What immediate steps should I take to mitigate this vulnerability?

The vulnerability involves a deadlock in the Linux kernel's drm/imagination soft reset sequence caused by the use of disable_irq() in a threaded IRQ handler.

To mitigate this vulnerability, update your Linux kernel to a version where this issue is fixed by using disable_irq_nosync() instead of disable_irq() during the soft reset sequence.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart