CVE Catalog

CVE-2026-93249

Unknown
Published: Translated: NVD NIST

Summary

In the spi: amlogic-spisg driver, the clk_init_data structure is not fully initialized, which may cause a crash when CONFIG_INIT_STACK_ALL_PATTERN or CONFIG_INIT_STACK_NONE is enabled. The issue involves the uninitialized parent_names field.

Risk Assessment

Incomplete initialization may cause system crashes during SPI driver operation, potentially leading to device unavailability or system failure. The risk is low but real in specific configurations.

Recommendation

It is recommended to update the Linux kernel to a version containing the fix that fully initializes the clk_init_data structure. Also, avoid enabling the mentioned configuration options if possible.

Other vulnerabilities in Linux kernel

See all
Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS