clk: visconti: Make sure clk_init_data is fully initialized (CVE-2026-90122) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-90122

clk: visconti: Make sure clk_init_data is fully initialized

Answer in brief

CVE-2026-90122 records a Unknown severity vulnerability in clk: visconti: Make sure clk_init_data is fully initialized. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 17, 2026Updated Sep 17, 2026Source checked Sep 17, 2026First seen by HOL Sep 17, 2026Material review Sep 17, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=b4cbe606dc3674b25cb661e7cd1a1c6ddaaafaaa <0e97c22b286e1918c6f48bad7e77fb8240a24b4a \|\| >=b4cbe606dc3674b25cb661e7cd1a1c6ddaaafaaa <9f756f1965bad65e6066608f33c36988cd10302a \|\| >=b4cbe606dc3674b25cb661e7cd1a1c6ddaaafaaa <1cc0539e5b0906bace15d3fc7347b344a017cc02 \|\| >=b4cbe606dc3674b25cb661e7cd1a1c6ddaaafaaa <8f7980033e9f7ecaaecd873a0b5bf6b6c87d7e5a \|\| >=b4cbe606dc3674b25cb661e7cd1a1c6ddaaafaaa <5ecfa72e74c6e2a765fa5bc1da574e5beae588f2 \|\| >=b4cbe606dc3674b25cb661e7cd1a1c6ddaaafaaa <39c0e6c844a14945040cca4ccf6997792ab764c4	0e97c22b286e1918c6f48bad7e77fb8240a24b4a, 9f756f1965bad65e6066608f33c36988cd10302a, 1cc0539e5b0906bace15d3fc7347b344a017cc02, 8f7980033e9f7ecaaecd873a0b5bf6b6c87d7e5a, 5ecfa72e74c6e2a765fa5bc1da574e5beae588f2, 39c0e6c844a14945040cca4ccf6997792ab764c4
Linux/Linuxgeneric	5.17	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to 0e97c22b286e1918c6f48bad7e77fb8240a24b4a if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 17, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.