CVE-2026-90122: clk: visconti: Make sure clk_init_data is fully initialized
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Fixed version: Linux Linux 0e97c22b286e1918c6f48bad7e77fb8240a24b4a, 1cc0539e5b0906bace15d3fc7347b344a017cc02, 39c0e6c844a14945040cca4ccf6997792ab764c4.
Low priority for now. Upgrade to Linux Linux 0e97c22b286e1918c6f48bad7e77fb8240a24b4a, 1cc0539e5b0906bace15d3fc7347b344a017cc02, 39c0e6c844a14945040cca4ccf6997792ab764c4 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 17, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.17affected
- b4cbe606dc3674b25cb661e7cd1a1c6ddaaafaaa and later · before 0e97c22b286e1918c6f48bad7e77fb8240a24b4aaffected · git
- b4cbe606dc3674b25cb661e7cd1a1c6ddaaafaaa and later · before 9f756f1965bad65e6066608f33c36988cd10302aaffected · git
- b4cbe606dc3674b25cb661e7cd1a1c6ddaaafaaa and later · before 1cc0539e5b0906bace15d3fc7347b344a017cc02affected · git
- b4cbe606dc3674b25cb661e7cd1a1c6ddaaafaaa and later · before 8f7980033e9f7ecaaecd873a0b5bf6b6c87d7e5aaffected · git
- b4cbe606dc3674b25cb661e7cd1a1c6ddaaafaaa and later · before 5ecfa72e74c6e2a765fa5bc1da574e5beae588f2affected · git
- b4cbe606dc3674b25cb661e7cd1a1c6ddaaafaaa and later · before 39c0e6c844a14945040cca4ccf6997792ab764c4affected · git
- before 5.17not affected · semver
- 6.1.188 and later · up to and including 6.1.*not affected · semver
- 6.6.157 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-90120Sep 17, 2026 · irqchip/gic-v5: Check get_logical_index() return value in MADT IAFFID parsing33Monitor
- ← EarlierCVE-2026-90121Sep 17, 2026 · irqchip/gic-v5: Clear per-CPU IRS data on teardown0Monitor
- Later →CVE-2026-90123Sep 17, 2026 · irqchip/ast2700-intc: Avoid allocating in the irq_domain activate() callback0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0e97c22b286e1918c6f48bad7e77fb8240a24b4a | Vendor (CNA) |
| Linux Linux | 1cc0539e5b0906bace15d3fc7347b344a017cc02 | Vendor (CNA) |
| Linux Linux | 39c0e6c844a14945040cca4ccf6997792ab764c4 | Vendor (CNA) |
| Linux Linux | 5ecfa72e74c6e2a765fa5bc1da574e5beae588f2 | Vendor (CNA) |
| Linux Linux | 8f7980033e9f7ecaaecd873a0b5bf6b6c87d7e5a | Vendor (CNA) |
| Linux Linux | 9f756f1965bad65e6066608f33c36988cd10302a | Vendor (CNA) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/1cc0539e5b0906bace15d3fc7347b344a017cc02
- git.kernel.org/stable/c/39c0e6c844a14945040cca4ccf6997792ab764c4
- git.kernel.org/stable/c/5ecfa72e74c6e2a765fa5bc1da574e5beae588f2
- git.kernel.org/stable/c/8f7980033e9f7ecaaecd873a0b5bf6b6c87d7e5a
- git.kernel.org/stable/c/9f756f1965bad65e6066608f33c36988cd10302a
Vendor advisories and official records. Exploit/PoC links are deliberately left out.