CVE-2026-23475 | Linux Kernel up to 7.0-rc4 spi null pointer dereference
VulDBArchived Apr 03, 2026✓ Full text saved
A vulnerability described as critical has been identified in Linux Kernel up to 7.0-rc4 . The impacted element is an unknown function of the component spi . The manipulation results in null pointer dereference. This vulnerability is cataloged as CVE-2026-23475 . The attack must originate from the local network. There is no exploit available. Upgrading the affected component is recommended.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-355165 · CVE-2026-23475 · GCVE-0-2026-23475
LINUX KERNEL UP TO 7.0-RC4 SPI NULL POINTER DEREFERENCE
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
5.5 $0-$5k 0.84
Summaryinfo
A vulnerability classified as critical has been found in Linux Kernel up to 7.0-rc4. This affects an unknown function of the component spi. This manipulation causes null pointer dereference. This vulnerability is registered as CVE-2026-23475. No exploit is available. It is recommended to upgrade the affected component.
Detailsinfo
A vulnerability was found in Linux Kernel up to 7.0-rc4. It has been declared as critical. Affected by this vulnerability is some unknown processing of the component spi. The manipulation with an unknown input leads to a null pointer dereference vulnerability. The CWE definition for the vulnerability is CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. As an impact it is known to affect availability. The summary by CVE is:
In the Linux kernel, the following vulnerability has been resolved: spi: fix statistics allocation The controller per-cpu statistics is not allocated until after the controller has been registered with driver core, which leaves a window where accessing the sysfs attributes can trigger a NULL-pointer dereference. Fix this by moving the statistics allocation to controller allocation while tying its lifetime to that of the controller (rather than using implicit devres).
The advisory is shared at git.kernel.org. This vulnerability is known as CVE-2026-23475 since 01/13/2026. Neither technical details nor an exploit are publicly available.
Upgrading to version 6.1.167, 6.6.130, 6.12.78, 6.18.20, 6.19.10 or 7.0-rc5 eliminates this vulnerability. Applying the patch 80c5bd0dca1cc5526ae0f4b273ccd163ed4caa4e/f13100b1f5f111989f0750540a795fdef47492af/df30056c78e8bead02d4be020199cabdbec0fef1/378b295f67102eef78cf2c28105f60ae1dab5cc1/118ce777d39f03cac99231196f820e4f998613a8/dee0774bbb2abb172e9069ce5ffef579b12b3ae9 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.1.166
6.6.129
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: 5.7
VulDB Meta Temp Score: 5.5
VulDB Base Score: 5.7
VulDB Temp Score: 5.5
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: Null pointer dereference
CWE: CWE-476 / 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.1.167/6.6.130/6.12.78/6.18.20/6.19.10/7.0-rc5
Patch: 80c5bd0dca1cc5526ae0f4b273ccd163ed4caa4e/f13100b1f5f111989f0750540a795fdef47492af/df30056c78e8bead02d4be020199cabdbec0fef1/378b295f67102eef78cf2c28105f60ae1dab5cc1/118ce777d39f03cac99231196f820e4f998613a8/dee0774bbb2abb172e9069ce5ffef579b12b3ae9
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-23475 (🔒)
GCVE (CVE): GCVE-0-2026-23475
GCVE (VulDB): GCVE-100-355165
Entryinfo
Created: 04/03/2026 18:17
Changes: 04/03/2026 18:17 (58)
Complete: 🔍
Cache ID: 99:5E7:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸