LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23475: spi: fix statistics allocation

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).

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

A timing flaw in the Linux SPI subsystem can cause a kernel NULL-pointer crash when SPI controller statistics are accessed through sysfs before their memory is allocated. The documented impact is system availability; the supplied sources do not establish data theft, code execution, or broader compromise.

Executive priority

Schedule remediation through the next controlled kernel maintenance cycle. Accelerate systems where SPI functionality supports availability-critical operations. Urgency cannot be rated precisely because no CVSS score, confirmed exploitation, or complete version-range interpretation is supplied.

Technical view

The kernel registers an SPI controller with the driver core before allocating its per-CPU statistics, creating a race window for sysfs access. The fix allocates statistics during controller allocation and ties their lifetime directly to the controller instead of implicit device-managed resources.

Likely exposure

Exposure is limited to Linux systems whose kernels contain the vulnerable SPI controller code and encounter sysfs access during controller registration. The supplied version data is ambiguous, so organizations should confirm affected status using kernel, distribution, or device-vendor advisories rather than version numbers alone.

Exploitation context

The supplied record is not in KEV and provides no evidence of active exploitation or a public exploit. Triggering requires access to affected sysfs attributes during a narrow registration window, but access prerequisites are not documented.

Researcher notes

The root cause is allocation ordering and resource lifetime management. The patch moves statistics allocation into controller allocation and releases it with the controller. The record establishes a NULL-pointer dereference window, but does not document reproducibility, required privileges, crash reliability, architectural reach, or consequences beyond availability.

Mitigation direction

  • Install a vendor-supported kernel update containing the referenced SPI statistics allocation fix.
  • If unavailable, consult the Linux distribution or device vendor for an approved mitigation and deployment timeline.
  • Prioritize SPI-dependent systems where an unexpected kernel crash would disrupt critical operations.

Validation and detection

  • Inventory running kernel builds and identify systems using SPI controllers or drivers.
  • Determine whether each running kernel includes an applicable referenced stable fix commit.
  • Check distribution and appliance advisories for confirmed affected status and corrected package versions.
  • After updating, monitor kernel logs for SPI-related NULL-pointer faults during controller initialization.
  • Confirm corrected kernels are running after reboot, not merely installed.
Prepared
Confidence
medium
Sources
8

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-23475 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
1ADP providers
9Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

siemens-SADPADP container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux6598b91b5ac32bc756d7c3000a31f775d4ead1c4, 6598b91b5ac32bc756d7c3000a31f775d4ead1c4, 6598b91b5ac32bc756d7c3000a31f775d4ead1c4, 6598b91b5ac32bc756d7c3000a31f775d4ead1c4, 6598b91b5ac32bc756d7c3000a31f775d4ead1c4, 6598b91b5ac32bc756d7c3000a31f775d4ead1c4unaffected
LinuxLinux6.0, 0, 6.1.167, 6.6.130, 6.12.78, 6.18.20, 6.19.10, 7.0affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.