CVE-2026-23470 | Linux Kernel up to 6.12.77/6.18.19/6.19.9/7.0-rc4 disable_irq deadlock
VulDBArchived Apr 03, 2026✓ Full text saved
A vulnerability labeled as critical has been found in Linux Kernel up to 6.12.77/6.18.19/6.19.9/7.0-rc4 . Impacted is the function disable_irq . Executing a manipulation can lead to deadlock. This vulnerability is tracked as CVE-2026-23470 . The attack is only possible within the local network. No exploit exists. The affected component should be upgraded.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-355163 · CVE-2026-23470 · GCVE-0-2026-23470
LINUX KERNEL UP TO 6.12.77/6.18.19/6.19.9/7.0-RC4 DISABLE_IRQ DEADLOCK
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
4.6 $0-$5k 0.93
Summaryinfo
A vulnerability marked as critical has been reported in Linux Kernel up to 6.12.77/6.18.19/6.19.9/7.0-rc4. The affected element is the function disable_irq. The manipulation leads to deadlock. This vulnerability is listed as CVE-2026-23470. There is no available exploit. It is suggested to upgrade the affected component.
Detailsinfo
A vulnerability was found in Linux Kernel up to 6.12.77/6.18.19/6.19.9/7.0-rc4 and classified as critical. This issue affects the function disable_irq. The manipulation with an unknown input leads to a deadlock vulnerability. Using CWE to declare the problem leads to CWE-833. The product contains multiple threads or executable segments that are waiting for each other to release a necessary lock, resulting in deadlock. Impacted is availability. The summary by CVE is:
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.
It is possible to read the advisory at git.kernel.org. The identification of this vulnerability is CVE-2026-23470 since 01/13/2026. The exploitation is known to be difficult. Technical details of the vulnerability are known, but there is no available exploit.
Upgrading to version 6.12.78, 6.18.20, 6.19.10 or 7.0-rc5 eliminates this vulnerability. Applying the patch f99e8b813ae5ce8ffd62c33f5753bf0a008af4b1/9497b1f309436971726e229aa6026954ea7c28e9/6f39b48a2d3b1fe83f99477250cd0cd67ca1e1c6/a55c2a5c8d680156495b7b1e2a9f5a3e313ba524 is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.
Productinfo
Type
Operating System
Vendor
Linux
Name
Kernel
Version
6.12.0
6.12.1
6.12.2
6.12.3
6.12.4
6.12.5
6.12.6
6.12.7
6.12.8
6.12.9
6.12.10
6.12.11
6.12.12
6.12.13
6.12.14
6.12.15
6.12.16
6.12.17
6.12.18
6.12.19
6.12.20
6.12.21
6.12.22
6.12.23
6.12.24
6.12.25
6.12.26
6.12.27
6.12.28
6.12.29
6.12.30
6.12.31
6.12.32
6.12.33
6.12.34
6.12.35
6.12.36
6.12.37
6.12.38
6.12.39
6.12.40
6.12.41
6.12.42
6.12.43
6.12.44
6.12.45
6.12.46
6.12.47
6.12.48
6.12.49
6.12.50
6.12.51
6.12.52
6.12.53
6.12.54
6.12.55
6.12.56
6.12.57
6.12.58
6.12.59
6.12.60
6.12.61
6.12.62
6.12.63
6.12.64
6.12.65
6.12.66
6.12.67
6.12.68
6.12.69
6.12.70
6.12.71
6.12.72
6.12.73
6.12.74
6.12.75
6.12.76
6.12.77
6.18.0
6.18.1
6.18.2
6.18.3
6.18.4
6.18.5
6.18.6
6.18.7
6.18.8
6.18.9
6.18.10
6.18.11
6.18.12
6.18.13
6.18.14
6.18.15
6.18.16
6.18.17
6.18.18
6.18.19
6.19.0
6.19.1
6.19.2
6.19.3
6.19.4
6.19.5
6.19.6
6.19.7
6.19.8
6.19.9
7.0-rc1
7.0-rc2
7.0-rc3
7.0-rc4
License
open-source
Website
Vendor: https://www.kernel.org/
CPE 2.3info
🔒
🔒
🔒
CPE 2.2info
🔒
🔒
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv3info
VulDB Meta Base Score: 4.8
VulDB Meta Temp Score: 4.6
VulDB Base Score: 4.8
VulDB Temp Score: 4.6
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2info
Vector Complexity Authentication Confidentiality Integrity Availability
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploitinginfo
Class: Deadlock
CWE: CWE-833 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Partially
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day Unlock Unlock Unlock Unlock
Today Unlock Unlock Unlock Unlock
Threat Intelligenceinfo
Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Countermeasuresinfo
Recommended: Upgrade
Status: 🔍
0-Day Time: 🔒
Upgrade: Kernel 6.12.78/6.18.20/6.19.10/7.0-rc5
Patch: f99e8b813ae5ce8ffd62c33f5753bf0a008af4b1/9497b1f309436971726e229aa6026954ea7c28e9/6f39b48a2d3b1fe83f99477250cd0cd67ca1e1c6/a55c2a5c8d680156495b7b1e2a9f5a3e313ba524
Timelineinfo
01/13/2026 CVE reserved
04/03/2026 +79 days Advisory disclosed
04/03/2026 +0 days VulDB entry created
04/03/2026 +0 days VulDB entry last update
Sourcesinfo
Vendor: kernel.org
Advisory: git.kernel.org
Status: Confirmed
CVE: CVE-2026-23470 (🔒)
GCVE (CVE): GCVE-0-2026-23470
GCVE (VulDB): GCVE-100-355163
Entryinfo
Created: 04/03/2026 18:16
Changes: 04/03/2026 18:16 (58)
Complete: 🔍
Cache ID: 99:029:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸