CVE-2026-93249
Received Received - Intake

Stack Overflow in Linux Kernel SPI Driver

Publication date: 2026-09-24

Last updated on: 2026-09-24

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: spi: amlogic-spisg: Make sure clk_init_data is fully initialized The clk_init_data structure contains several mutually-exclusive members for different methods to specify the possible parents of a clock, prompting drivers to initialize only the members they need. However, not initializing all members may cause subtle issues, which are only exposed when CONFIG_INIT_STACK_ALL_PATTERN or CONFIG_INIT_STACK_NONE is enabled. aml_spisg_clk_init() fills in init.parent_data, and assumes that init.parent_names is NULL. However, the latter in uninitialized, and thus may cause a crash. Make sure all members are fully initialized, to fix such bugs, and to avoid future breakage when converting drivers to a different method for specifying the parents.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-24
Last Modified
2026-09-24
Generated
2026-09-24
AI Q&A
2026-09-24
EPSS Evaluated
N/A
NVD
CVE-2026-93249
EUVD
EUVD-2026-86261

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
amlogic amlogic-spisg *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a Linux kernel vulnerability in the amlogic-spisg SPI controller driver. It involves incomplete initialization of the clk_init_data structure, which can lead to crashes when certain kernel configuration options are enabled. The driver assumes one parent data field is NULL but fails to initialize another, causing potential memory corruption or system instability.

Detection Guidance

This vulnerability is specific to the Linux kernel's spi: amlogic-spisg driver and may not have direct network detection methods. Check if your kernel version includes the affected driver by running uname -a and inspecting the spi subsystem. Look for crashes or stack traces related to spi operations.

Impact Analysis

If exploited, this could cause system crashes or instability on affected Linux systems using the amlogic-spisg SPI controller. It may lead to denial-of-service conditions or unexpected behavior in systems relying on SPI communication.

Mitigation Strategies

Update your Linux kernel to the latest stable version that includes the fix for this vulnerability. If updating is not immediately possible, disable the amlogic-spisg driver by blacklisting it in your kernel modules configuration.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-93249. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart