{"schemaVersion":1,"url":"https://cve.openhack.com/cve/CVE-2026-98667","id":"CVE-2026-98667","title":"iio: frequency: adf4377: Fully initialize clk_init_data and clk_parent_data","description":"In the Linux kernel, the following vulnerability has been resolved:\n\niio: frequency: adf4377: Fully initialize clk_init_data and clk_parent_data\n\nThe clk_init_data structure contains several mutually-exclusive members\nfor different methods to specify the possible parents of a clock,\nprompting drivers to initialize only the members they need.  However,\nnot initializing all members may cause subtle ","descriptionLong":"In the Linux kernel, the following vulnerability has been resolved:\n\niio: frequency: adf4377: Fully initialize clk_init_data and clk_parent_data\n\nThe clk_init_data structure contains several mutually-exclusive members\nfor different methods to specify the possible parents of a clock,\nprompting drivers to initialize only the members they need.  However,\nnot initializing all members may cause subtle issues, which are only\nexposed when CONFIG_INIT_STACK_ALL_PATTERN or CONFIG_INIT_STACK_NONE is\nenabled.\n\nadf4377_clk_register() fills in init.parent_data, and assumes that\ninit.parent_names is NULL.  However, the latter is uninitialized, and\nthus may cause a crash.\n\nSimilarly, adf4377_clk_register() fills in only parent_data.fw_name,\nleaving other members of the clk_parent_data structure uninitialized.\n\nMake sure all members are fully initialized, to fix such bugs, and to\navoid future breakage when converting drivers to a different method for\nspecifying the parents.","published":"2026-10-18T15:44:51.640Z","updated":"2026-10-28T02:30:56.018825692Z","reserved":"2026-09-25T10:25:14.363Z","status":"Received","rejected":false,"assigner":"Linux","metric":null,"metrics":[],"rating":"unrated","products":["Linux"],"affectedProducts":[{"vendor":"Linux","product":"Linux","defaultStatus":"unaffected","versions":[{"version":"60e5448ddbec2dc206027a4850604d8fdf9973b7","lessThan":"6564f394a4a95fad534643a6ca0f1d36ff081799","status":"affected","versionType":"git"},{"version":"60e5448ddbec2dc206027a4850604d8fdf9973b7","lessThan":"e787fd23d5063c61582c3c27522240b6e6703fde","status":"affected","versionType":"git"}],"platforms":[]},{"vendor":"Linux","product":"Linux","defaultStatus":"affected","versions":[{"version":"7.0","status":"affected"},{"version":"0","lessThan":"7.0","status":"unaffected","versionType":"semver"},{"version":"7.2.10","lessThanOrEqual":"7.2.*","status":"unaffected","versionType":"semver"},{"version":"7.3","lessThanOrEqual":"*","status":"unaffected","versionType":"original_commit_for_fix"}],"platforms":[]}],"packages":[],"cwes":[],"aliases":[],"references":[{"url":"https://git.kernel.org/stable/c/6564f394a4a95fad534643a6ca0f1d36ff081799","tags":["web"]},{"url":"https://git.kernel.org/stable/c/e787fd23d5063c61582c3c27522240b6e6703fde","tags":["web"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/98xxx/CVE-2026-98667.json","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-98667","tags":["advisory"]},{"url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","tags":["package"]}],"patchReferenced":false,"fixAvailable":false,"exploitReferenced":false,"kev":false,"kevAdded":null,"kevDue":null,"kevEntry":null,"ssvc":null,"epss":0.00155,"epssPercentile":0.04778,"sources":[{"name":"CVE List","url":"https://www.cve.org/CVERecord?id=CVE-2026-98667","ok":true},{"name":"NVD","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-98667","ok":true,"note":"Received"},{"name":"OSV","url":"https://osv.dev/vulnerability/CVE-2026-98667","ok":true,"note":"0 packages"},{"name":"CISA KEV","url":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","ok":true,"note":"not listed"},{"name":"EPSS","url":"https://api.first.org/data/v1/epss?cve=CVE-2026-98667","ok":true,"note":"scored 2026-11-19"}],"aiTitle":false,"tech":[],"critical":[],"attention":null}