CVE-2026-98667
Last modified
CVE-2026-98667 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: iio: frequency: adf4377: Fully initialize clk_init_data and clk_parent_data 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. adf4377_clk_register() fills in init.parent_data, and assumes that init.parent_names is NULL.
Description
In the Linux kernel, the following vulnerability has been resolved: iio: frequency: adf4377: Fully initialize clk_init_data and clk_parent_data 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. adf4377_clk_register() fills in init.parent_data, and assumes that init.parent_names is NULL. However, the latter is uninitialized, and thus may cause a crash. Similarly, adf4377_clk_register() fills in only parent_data.fw_name, leaving other members of the clk_parent_data structure uninitialized. 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.
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 60e5448ddbec2dc206027a4850604d8fdf9973b7, < 6564f394a4a95fad534643a6ca0f1d36ff081799; >= 60e5448ddbec2dc206027a4850604d8fdf9973b7, < e787fd23d5063c61582c3c27522240b6e6703fde |
| Linux | Linux | 7.0 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-98667?
How severe is CVE-2026-98667?
How do I fix CVE-2026-98667?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-98661In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98662In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98663In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98664In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98665In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98666In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98668In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98669In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98670In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98671In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98672In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98673In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-98667?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
