Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 32 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (14 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected b4cbe606dc3674b25cb661e7cd1a1c6ddaaafaaa – < 0e97c22b286e1918c6f48bad7e77fb8240a24b4a
    • affected b4cbe606dc3674b25cb661e7cd1a1c6ddaaafaaa – < 9f756f1965bad65e6066608f33c36988cd10302a
    • affected b4cbe606dc3674b25cb661e7cd1a1c6ddaaafaaa – < 1cc0539e5b0906bace15d3fc7347b344a017cc02
    • affected b4cbe606dc3674b25cb661e7cd1a1c6ddaaafaaa – < 8f7980033e9f7ecaaecd873a0b5bf6b6c87d7e5a
    • affected b4cbe606dc3674b25cb661e7cd1a1c6ddaaafaaa – < 5ecfa72e74c6e2a765fa5bc1da574e5beae588f2
    • affected b4cbe606dc3674b25cb661e7cd1a1c6ddaaafaaa – < 39c0e6c844a14945040cca4ccf6997792ab764c4
  • Linux · Linux

    • affected 5.17
    • unaffected < 5.17
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-90122 badge
[![CVE-2026-90122](https://cveledger.app/badge/CVE-2026-90122.svg)](https://cveledger.app/cve/CVE-2026-90122)

Record last updated .