CVE-2026-93825Hinoki check available

Local kernel crash via unmatched SPI override

Published Sep 24, 2026 · Updated Sep 24, 2026

NULL pointer dereference in Linux kernel SPI before 6.12.111 and 6.18.53 allows local users to crash the system via driver_override. The spi_get_device_match_data() fallback dereferences the result of spi_get_device_id() without checking whether an overridden driver has a matching SPI ID entry. Reaching the fault requires local permission to modify SPI driver override and binding controls; the resulting NULL dereference can crash the kernel.

CVSS severityUnavailable
Unscored
EPSS probability0.17%
Next 30 days · Oct 19, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkAvailable
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Get started

Summary

What happened

NULL pointer dereference in Linux kernel SPI before 6.12.111 and 6.18.53 allows local users to crash the system via driver_override. The spi_get_device_match_data() fallback dereferences the result of spi_get_device_id() without checking whether an overridden driver has a matching SPI ID entry. Reaching the fault requires local permission to modify SPI driver override and binding controls; the resulting NULL dereference can crash the kernel.

The record

CVE
CVE-2026-93825
Published
Sep 24, 2026
Updated
Sep 24, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
T1499
Attack vector
local
Privileges
Unavailable

Timeline

How it unfolded

  1. Sep 24, 2026CVE publishedPublication date reported by the CVE source.
  2. Sep 24, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <6.12.111
  2. Affected versionversion=0 <6.18.53
  3. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3fcd9415144f4fbd21e1bef35a7f8dbd734f607d
  4. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <72cc9c6d6fba5b4e0aaf89126884a56bb54b92f8
  5. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f1b061b4d4c6cbf861319ba954caa80145cf018f

What conditions does exploitation require?

Attack vectorlocal
Required privilegesUnavailable in this record.

What is affected?

The Linux Kernel Organization · Linuxversion=0 <6.12.111; version=0 <6.18.53; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3fcd9415144f4fbd21e1bef35a7f8dbd734f607d; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <72cc9c6d6fba5b4e0aaf89126884a56bb54b92f8; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f1b061b4d4c6cbf861319ba954caa80145cf018f

Published CVSS scores

No CVSS assessment is available in this record.

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Activity data is delayed. The latest report is Sep 28, 2026.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 22, 2026Sep 28, 2026
Latest reporting daySep 28, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
PrivilegesUnavailable
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

T1499Endpoint Denial of Service

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Get started to see how Hinoki identifies affected software and validates exploitability in your environment.

Get started