CVE-2026-90122

clk: visconti: Make sure clk_init_data is fully initialized

State
Published
Severity
Not scored
Published
Sep 17, 2026
Updated
Oct 19, 2026
Reserved
Sep 11, 2026

Read the record on cve.org

Description

In the Linux kernel, the following vulnerability has been resolved:

clk: visconti: 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.

visconti_clk_register_gate() 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.

Scores

The record has no CVSS score.

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • b4cbe606dc3674b25cb661e7cd1a1c6ddaaafaaa to before 0e97c22b286e1918c6f48bad7e77fb8240a24b4aAffected
  • b4cbe606dc3674b25cb661e7cd1a1c6ddaaafaaa to before 9f756f1965bad65e6066608f33c36988cd10302aAffected
  • b4cbe606dc3674b25cb661e7cd1a1c6ddaaafaaa to before 1cc0539e5b0906bace15d3fc7347b344a017cc02Affected
  • b4cbe606dc3674b25cb661e7cd1a1c6ddaaafaaa to before 8f7980033e9f7ecaaecd873a0b5bf6b6c87d7e5aAffected
  • b4cbe606dc3674b25cb661e7cd1a1c6ddaaafaaa to before 5ecfa72e74c6e2a765fa5bc1da574e5beae588f2Affected
  • b4cbe606dc3674b25cb661e7cd1a1c6ddaaafaaa to before 39c0e6c844a14945040cca4ccf6997792ab764c4Affected
LinuxLinux
  • 5.17Affected
  • before 5.17Not affected
  • 6.1.188 through 6.1.*Not affected
  • 6.6.157 through 6.6.*Not affected
  • 6.12.110 through 6.12.*Not affected
  • 6.18.52 through 6.18.*Not affected
  • 7.2.6 through 7.2.*Not affected
  • 7.3 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.