clk: visconti: Make sure clk_init_data is fully initialized
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.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.1.188, 6.12.110, 6.18.52, 6.6.157, 7.2.6
- CVEs
- CVE-2026-90122
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 4 Nov 2026, 02:35 UTC · Revision 1
Source evidence
clk: visconti: Make sure clk_init_data is fully initialized
core-osv · Original sourcePublished 17 Sept 2026, 16:06 UTC
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.
osv:CVE-2026-90122
Kernel
Fixed versions: 6.1.188, 6.6.157, 6.12.110, 6.18.52, 7.2.6
Complete source record
{
"id": "cfbf064e5a2c35889ea263c8da80e036c6dce2e9adb4a1eb4fd1685bcd12d7ac",
"url": "https://osv.dev/vulnerability/CVE-2026-90122",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "clk: visconti: Make sure clk_init_data is fully initialized",
"summary": "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.",
"evidence": "osv:CVE-2026-90122",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.1.188",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.157",
"evidence": "/affected/1/ranges"
},
{
"value": "6.12.110",
"evidence": "/affected/1/ranges"
},
{
"value": "6.18.52",
"evidence": "/affected/1/ranges"
},
{
"value": "7.2.6",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2026-90122",
"aliases": [
"CVE-2026-90122"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "b4cbe606dc3674b25cb661e7cd1a1c6ddaaafaaa"
},
{
"fixed": "0e97c22b286e1918c6f48bad7e77fb8240a24b4a"
},
{
"fixed": "9f756f1965bad65e6066608f33c36988cd10302a"
},
{
"fixed": "1cc0539e5b0906bace15d3fc7347b344a017cc02"
},
{
"fixed": "8f7980033e9f7ecaaecd873a0b5bf6b6c87d7e5a"
},
{
"fixed": "5ecfa72e74c6e2a765fa5bc1da574e5beae588f2"
},
{
"fixed": "39c0e6c844a14945040cca4ccf6997792ab764c4"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-90122.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.17.0"
},
{
"fixed": "6.1.188"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.157"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.12.110"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.18.52"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "7.2.6"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-90122.json"
}
}
],
"modified": "2026-10-28T02:30:32.623225055Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/0e97c22b286e1918c6f48bad7e77fb8240a24b4a",
"https://git.kernel.org/stable/c/1cc0539e5b0906bace15d3fc7347b344a017cc02",
"https://git.kernel.org/stable/c/39c0e6c844a14945040cca4ccf6997792ab764c4",
"https://git.kernel.org/stable/c/5ecfa72e74c6e2a765fa5bc1da574e5beae588f2",
"https://git.kernel.org/stable/c/8f7980033e9f7ecaaecd873a0b5bf6b6c87d7e5a",
"https://git.kernel.org/stable/c/9f756f1965bad65e6066608f33c36988cd10302a",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/90xxx/CVE-2026-90122.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-90122",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/90xxx/CVE-2026-90122.json"
}
},
"related_cves": [
{
"value": "CVE-2026-90122",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 499726,
"published_at": "2026-09-17T16:06:25.91+00:00"
}