CVE-2026-93249 spi: amlogic-spisg: Make sure clk_init_data is fully initialized

Not scored Published Updated

A null pointer dereference in the Amlogic SPI driver can cause a kernel crash if specific initialization stack patterns are enabled.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Local or same network only
Victim action needed
Not needed
Fix
Available

What is CVE-2026-93249?

CVE-2026-93249 is a vulnerability in Linux, published on 24 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

Official 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.

Which versions are affected by CVE-2026-93249?

How do I fix CVE-2026-93249?

Apply the vendor's patch.

Is CVE-2026-93249 being exploited?

There is no known exploitation of CVE-2026-93249 in the wild and no public exploit code.

Sources

Also known as BELL-CVE-2026-93249, DEBIAN-CVE-2026-93249, GHSA-m9p6-55m4-wcwq, UBUNTU-CVE-2026-93249.

Is CVE-2026-93249 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free