Quick answers
- Is CVE-2026-93825 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-93825 being exploited in the wild.
- How severe is CVE-2026-93825?
- Informational severity, published 24 September 2026.
- Which products and versions are affected?
- Linux Multiple versions across 2.6.11 through 7.2 series.
- Is there a fix for CVE-2026-93825?
- A patch was published on 2026-06-16: Patch committed upstream before disclosure Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-93825 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-93825?
- Check whether you run Linux at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The spi_get_device_match_data() function in drivers/spi/spi.c failed to check whether spi_get_device_id() returned NULL before dereferencing the returned pointer. This occurs when driver_override is used without a corresponding SPI ID table entry. The fix adds a NULL check before dereferencing the pointer. Local attack vector; requires ability to trigger device driver loading with crafted driver_override configuration.
Affected products
- Linux Linux Multiple versions across 2.6.11 through 7.2 series
Timeline
- 2026-09-24: disclosed
- 2026-06-16: patched: Patch committed upstream before disclosure
- 2026-09-21: other: Merged into stable kernel trees