CVE-2026-98001
Last modified
CVE-2026-98001 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: hwmon: (ltc4282) 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. ltc428_clk_provider_setup() does not fill in any parent clocks, and assumes that init.num_parents is NULL.
Description
In the Linux kernel, the following vulnerability has been resolved: hwmon: (ltc4282) 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. ltc428_clk_provider_setup() does not fill in any parent clocks, and assumes that init.num_parents 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.
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= cbc29538dbf7d7400f1ffc5dd5713e6a551463a0, < c4a96da5a3f132d80aa971ddbeb86808539ba0e6; >= cbc29538dbf7d7400f1ffc5dd5713e6a551463a0, < 80b46a3d066d4e2c1dd4edb90d4aa3f22ca79f39; >= cbc29538dbf7d7400f1ffc5dd5713e6a551463a0, < aa08ce1ffaf36c7bdd3edd0ad65f72413639bfad; >= cbc29538dbf7d7400f1ffc5dd5713e6a551463a0, < e317326d1755ea054b98e7a4833b929157461c35 |
| Linux | Linux | 6.9 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-98001?
How severe is CVE-2026-98001?
How do I fix CVE-2026-98001?
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-97995In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97996In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97997In the Linux kernel, the following vulnerability has been re…
- CVE-2026-97998In the Linux kernel, the following vulnerability has been re…
- CVE-2026-9800A flaw was found in Keycloak Policy Enforcer. This vulnerabi…8.1
- CVE-2026-98000In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98002In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-98003In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98004In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98005In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98006In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98007In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-98001?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
