How to Fix CVE-2026-23475: Linux (Bundle Sibling)

*By Sai Kiran Pandrala*

Last verified: 2026-05-25

CVE-2026-23475 is a sibling vulnerability in the same Linux Linux advisory bundle as CVE-2026-23401. The same patched build closes every CVE in the bundle, so the remediation procedure for CVE-2026-23475 matches the primary write-up.

What is different about CVE-2026-23475?

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

Impact is consistent with the bundle: compromise of the affected component as described in the vendor advisory. The patched build closes every code path in the advisory in one update.

How to fix CVE-2026-23475

Apply the patched build per the primary write-up: How to Fix CVE-2026-23401.

For a quick check, confirm the running version of Linux:

# Confirm the installed version via your package manager
dpkg -l | grep -i linux   # Debian/Ubuntu
rpm -qa | grep -i linux   # RHEL/CentOS/Rocky

Frequently asked questions

Is CVE-2026-23475 being actively exploited?

Not at the time of writing. It is not listed in CISA's Known Exploited Vulnerabilities catalog. That status can change, so monitor the vendor advisory and the KEV catalog if the system is exposed.

How severe is CVE-2026-23475?

CVSS has not been published in the data sources used for this page. Refer to the vendor advisory and NVD for any score updates.

Do I have to take Linux offline to apply the patch?

It depends on the deployment. High-availability or clustered installs can usually patch one node at a time with no full outage. Standalone installs typically need a short restart. Always follow the vendor's documented upgrade steps.

What if my vulnerability scanner still flags CVE-2026-23475 after I patch?

Re-run the scan after a service restart, then confirm the scanner's plugin set is up to date. Some scanners detect by banner version only and lag the official fix metadata by a release.

References

• Official vendor advisory: https://git.kernel.org/stable/c/80c5bd0dca1cc5526ae0f4b273ccd163ed4caa4e
• NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2026-23475
• CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
• Primary write-up: How to Fix CVE-2026-23401

*Written by Sai Kiran Pandrala. Last verified 2026-05-25. Part of the Linux Linux advisory bundle. Full procedure at how-to-fix-cve-2026-23401.*