CVE-2026-98001: hwmon: (ltc4282) Make sure clk_init_data is fully initialized
In the Linux kernel, the following vulnerability has been resolved:
hwmon: (ltc4282) Make sure clkinitdata is fully initialized
The clkinitdata 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 CONFIGINITSTACKALLPATTERN or CONFIGINITSTACKNONE is enabled.
ltc428clkprovidersetup() does not fill in any parent clocks, and assumes that init.numparents 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.
Affected Software
Event History
Frequently Asked Questions
Which systems are most likely to encounter this issue?
Systems running the Linux kernel with the ltc4282 hardware-monitor driver are relevant. The crash condition is exposed when CONFIG_INIT_STACK_ALL_PATTERN or CONFIG_INIT_STACK_NONE is enabled.
What condition triggers the failure?
The ltc428_clk_provider_setup() path leaves mutually exclusive clk_init_data members uninitialized while assuming init.num_parents is NULL. If the uninitialized value is non-NULL, clock-provider setup may crash.
Is there a configuration-based mitigation if an update cannot be applied immediately?
The described issue is only exposed with CONFIG_INIT_STACK_ALL_PATTERN or CONFIG_INIT_STACK_NONE enabled. Avoiding those configurations removes the stated trigger, though the underlying driver initialization defect remains.