CVE-2026-93825

A flaw was found in the Linux kernel's Serial Peripheral Interface (SPI) subsystem. This vulnerability allows a local user to cause a Denial of Service (DoS) through a system crash. The issue occurs because the spi_get_device_match_data() function does not verify whether a device identifier exists before accessing it, leading to a NULL pointer dereference when a driver override is configured without a matching SPI entry.

Red Hat has rated this flaw as having Low security impact. A NULL pointer dereference flaw was found in the Linux kernel's Serial Peripheral Interface (SPI) subsystem: the spi_get_device_match_data() helper does not verify that spi_get_device_id() returned a valid device identifier before accessing it. When driver_override is used to bind a driver to an SPI device that has no matching SPI ID table entry, spi_get_device_id() returns NULL and the resulting dereference causes a kernel crash, resulting in a denial of service. Triggering the flaw requires local access together with the privileges needed to configure the sysfs driver_override attribute, and the impact is limited to availability. While the Red Hat CVSS:3.1 base score of 5.5 (Moderate) reflects the high availability impact, the required local privileged access and the denial-of-service-only consequence lead Red Hat to rate the overall security impact as Low. The vulnerable code is not present in Red Hat Enterprise Linux 6, 7, and 8, in RHEL 9.2 and 9.4, or in OpenShift Container Platform 4.12 through 4.18, so those products are not affected. For the affected products (Red Hat Enterprise Linux 9 and 10, Red Hat In-Vehicle OS 2, and OpenShift Container Platform 4.19 and later), the fix has been deferred to a future planned update because of the low severity and the limited attack vector; the residual risk is a local denial of service caused by a user who already holds the privileges required to configure SPI driver_override.

The CVSS score(s) listed for this vulnerability do not reflect the associated product's status, and are included for informational purposes to better understand the severity of this vulnerability.

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.