# CVE-2026-90122: clk: visconti: Make sure clk_init_data is fully initialized

> A missing initialization in the Visconti clock driver can cause a kernel crash, leading to denial of service under specific configuration settings.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-102447, BELL-CVE-2026-90122, DEBIAN-CVE-2026-90122, GHSA-chc4-v67r-8fwq, UBUNTU-CVE-2026-90122

## What is CVE-2026-90122?

CVE-2026-90122 is a vulnerability in Linux, published on 17 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:

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.

## Which versions are affected by CVE-2026-90122?


## How do I fix CVE-2026-90122?

Apply the vendor's patch.

## Is CVE-2026-90122 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-90122 and fix it if it is affected.

What it is: CVE-2026-90122 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-90122 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-90122/ (Markdown: https://insights.sbomify.com/CVE-2026-90122/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-90122
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-90122
- OSV: https://osv.dev/vulnerability/CVE-2026-90122

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-90122/
Summaries are generated and may contain mistakes; the official description above is the record.