iio: frequency: adf4377: Fully initialize clk_init_data and clk_parent_data
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 6564f394a4a95fad534643a6ca0f1d36ff081799 and Kernel e787fd23d5063c61582c3c27522240b6e6703fde.
In the Linux kernel, the following vulnerability has been resolved: iio: frequency: adf4377: Fully initialize clk_init_data and clk_parent_data 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. adf4377_clk_register() fills in init.parent_data, and assumes that init.parent_names is NULL. However, the latter is uninitialized, and thus may cause a crash. Similarly, adf4377_clk_register() fills in only parent_data.fw_name, leaving other members of the clk_parent_data structure uninitialized. 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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =7.0, >=60e5448ddbec2dc206027a4850604d8fdf9973b7 <6564f394a4a95fad534643a6ca0f1d36ff081799, >=60e5448ddbec2dc206027a4850604d8fdf9973b7 <e787fd23d5063c61582c3c27522240b6e6703fde | 6564f394a4a95fad534643a6ca0f1d36ff081799, e787fd23d5063c61582c3c27522240b6e6703fde |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket