{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98667 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98667 is a vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-98667 and fix it if it is affected.\n\nWhat it is: CVE-2026-98667 is a vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-98667 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-98667/ (Markdown: https://insights.sbomify.com/CVE-2026-98667/index.md)","id":"CVE-2026-98667","markdown":"https://insights.sbomify.com/CVE-2026-98667/index.md","name":"CVE-2026-98667","record":{"aliases":["DEBIAN-CVE-2026-98667","GHSA-xcxr-v5jx-qv69","UBUNTU-CVE-2026-98667"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel driver","requires_auth":"none","summary":"Uninitialized kernel structure members in the ADF4377 driver can cause a system crash, requiring specific kernel configurations to trigger.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"iio: frequency: adf4377: Fully initialize clk_init_data and clk_parent_data","id":"CVE-2026-98667","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"iio: buffer: Ensure bounce buffer used for unaligned case is zeroed.","id":"CVE-2026-98668"},"packages":[],"prev":{"headline":"iio: gyro: adis16136: fix unprotected debugfs reads","id":"CVE-2026-98666"},"products":["Linux"],"published":"2026-10-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"Uninitialized kernel structure members in the ADF4377 driver can cause a system crash, requiring specific kernel configurations to trigger.","url":"https://insights.sbomify.com/CVE-2026-98667/"}