{"id":"CVE-2026-98667","kind":"vulnerability","aliases":["CVE-2026-98667"],"related":[],"title":"Linux kernel: ADF4377 clock driver can read uninitialized parent fields","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 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.","summary":"The Linux kernel's ADF4377 IIO frequency driver left parts of its clock init structures uninitialized, which can cause a crash when the kernel is built with stack-initialization debug options. The sources describe a stability bug with no stated remote exploit path.","severity":"unknown","cvss":null,"epss":null,"exploited":false,"exploited_at":null,"products":[],"ecosystems":[],"tags":["embedded","iio","infrastructure","linux-kernel"],"not_affected_if":["adf4377-driver-not-loaded","default-stack-init-config"],"how_to_check":"- unknown","fix":"- Update to a Linux kernel release that includes the upstream fix for the adf4377 clock initialization (commit not named in the sources)","status":"open","published_at":"2026-10-18T16:17:19+00:00","first_seen_at":"2026-10-23T21:57:16+00:00","triaged_at":"2026-10-25T05:19:24+00:00","updated_at":"2026-10-25T05:19:24+00:00","category":"infrastructure","confidence":0.5,"triage":{"at":"2026-10-25T05:19:24Z","model":"claude-haiku-5-5","output":{"fix":"- Update to a Linux kernel release that includes the upstream fix for the adf4377 clock initialization (commit not named in the sources)","reach":"local","title":"Linux kernel: ADF4377 clock driver can read uninitialized parent fields","impact":"low","summary":"The Linux kernel's ADF4377 IIO frequency driver left parts of its clock init structures uninitialized, which can cause a crash when the kernel is built with stack-initialization debug options. The sources describe a stability bug with no stated remote exploit path.","category":"infrastructure","nicknames":[],"who_cares":["linux-kernel","embedded","iio"],"confidence":0.5,"needs_auth":"unknown","worst_case":"kernel crash from uninitialized clock parent data","analyst_note":"","how_to_check":"- unknown","needs_analyst":false,"not_affected_if":["adf4377-driver-not-loaded","default-stack-init-config"],"who_is_affected":"Systems running a Linux kernel with the adf4377 driver loaded, typically embedded or RF hardware using the ADF4377 frequency synthesizer. The bug only surfaces when CONFIG_INIT_STACK_ALL_PATTERN or CONFIG_INIT_STACK_NONE is enabled, so default-config kernels are less likely to hit it. unknown for whether a standard distribution kernel is affected.","user_interaction":"no","needs_special_setup":"yes","severity_if_unknown":"low"},"cost_usd":0.000614,"input_tokens":3565,"output_tokens":514,"severity_before":"unknown"},"analyst_status":null,"analyst_note":null,"search":"'-2026':12A,15A '-98667':13A,16A 'adf4377':3A,27B,79C,146C,172C 'assum':154C 'avoid':203C 'breakag':205C 'bug':60B,200C 'built':48B 'caus':41B,126C,168C 'clk':82C,86C,90C,147C,173C,185C 'clock':4A,35B,110C 'config':134C,140C 'contain':94C 'convert':207C 'crash':43B,170C 'cve':11A,14A 'data':84C,88C,92C,152C,187C 'debug':53B 'describ':57B 'differ':101C,211C 'driver':5A,30B,112C,208C 'embed':17B 'enabl':145C 'exclus':98C 'exploit':65B 'expos':132C 'field':10A 'fill':149C,175C 'fix':198C 'follow':72C 'frequenc':29B,78C 'fulli':80C,195C 'futur':204C 'howev':120C,160C 'iio':18B,28B,77C 'infrastructur':19B 'init':36B,83C,91C,135C,141C 'init.parent':151C,156C 'initi':52B,81C,114C,122C,196C 'issu':128C 'kernel':2A,22B,25B,46B,70C 'latter':162C 'leav':180C 'left':31B 'linux':1A,21B,24B,69C 'linux-kernel':20B 'make':190C 'may':125C,167C 'member':99C,117C,124C,182C,193C 'method':102C,212C 'mutual':97C 'mutually-exclus':96C 'name':157C,179C 'need':119C 'none':143C 'null':159C 'option':54B 'parent':9A,87C,107C,186C,216C 'parent_data.fw':178C 'part':32B 'path':66B 'pattern':138C 'possibl':106C 'prompt':111C 'read':7A 'regist':148C,174C 'remot':64B 'resolv':76C 'sever':95C 'similar':171C 'sourc':56B 'specifi':104C,214C 'stabil':59B 'stack':51B,136C,142C 'stack-initi':50B 'state':63B 'structur':37B,93C,188C 'subtl':127C 'sure':191C 'thus':166C 'uniniti':8A,38B,164C,189C 'vulner':73C","nicknames":[],"mitigations":[],"who_affected":"Systems running a Linux kernel with the adf4377 driver loaded, typically embedded or RF hardware using the ADF4377 frequency synthesizer. The bug only surfaces when CONFIG_INIT_STACK_ALL_PATTERN or CONFIG_INIT_STACK_NONE is enabled, so default-config kernels are less likely to hit it. unknown for whether a standard distribution kernel is affected.","tier":"C","verified":{},"analyst_revisit_at":null,"first_public_at":"2026-10-18T16:17:19+00:00","kev":null,"cvss_vector":null,"cvss_by":null,"poc_count":0,"sources":[{"source":"nvd","external_id":"CVE-2026-98667","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-98667","severity":null,"published_at":"2026-10-18T16:17:19+00:00","modified_at":"2026-10-19T10:19:31+00:00","first_seen_at":"2026-10-23T21:57:16+00:00","fetched_at":"2026-10-23T22:28:56+00:00","note":null}],"documents":[],"notice":"Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai"}