linux: In the Linux kernel, the following vulnerability has been resolved: drm/imagination: Fix deadlock in soft reset sequ...
CVE-2026-23470 is fixed in 11 products on 1 platform, first by DEBIAN-CVE-2026-23470, released April 3, 2026. It is not reported as exploited. Patch Radar priority: Routine.
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.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| kernel-64kb · sles 15.7 | 6.4.0-150700.53.55.1 | SUSE-SU-2026:2238-1 | Jun 30, 2026 |
| kernel-azure · sles 15.7 | 6.4.0-150700.53.55.1 | SUSE-SU-2026:2238-1 | Jun 30, 2026 |
| kernel-default · sles 15.7 | 6.4.0-150700.53.55.1 | SUSE-SU-2026:2238-1 | Jun 30, 2026 |
| kernel-default-base · sles 15.7 | 6.4.0-150700.53.55.1.150700.17.33.1 | SUSE-SU-2026:2238-1 | Jun 30, 2026 |
| kernel-docs · sles 15.7 | 6.4.0-150700.53.55.1 | SUSE-SU-2026:2238-1 | Jun 30, 2026 |
| kernel-livepatch-SLE15-SP7_Update_15 · sles 15.7 | 1-150700.15.3.1 | SUSE-SU-2026:2238-1 | Jun 30, 2026 |
| kernel-obs-build · sles 15.7 | 6.4.0-150700.53.55.1 | SUSE-SU-2026:2238-1 | Jun 30, 2026 |
| kernel-source · sles 15.7 | 6.4.0-150700.53.55.1 | SUSE-SU-2026:2238-1 | Jun 30, 2026 |
| kernel-syms · sles 15.7 | 6.4.0-150700.53.55.1 | SUSE-SU-2026:2238-1 | Jun 30, 2026 |
| kernel-zfcpdump · sles 15.7 | 6.4.0-150700.53.55.1 | SUSE-SU-2026:2238-1 | Jun 30, 2026 |
| linux · Debian 13.5 (trixie) | 6.12.85-1 | DEBIAN-CVE-2026-23470 | Apr 3, 2026 |
| linux · Debian 14 | 6.19.10-1 | DEBIAN-CVE-2026-23470 | Apr 3, 2026 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.