hwmon: (ltc4282) Make sure clk_init_data is fully initialized (CVE-2026-98001) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-98001

hwmon: (ltc4282) Make sure clk_init_data is fully initialized

Answer in brief

CVE-2026-98001 records a Unknown severity vulnerability in hwmon: (ltc4282) Make sure clk_init_data is fully initialized. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 25, 2026Updated Sep 25, 2026Source checked Sep 25, 2026First seen by HOL Sep 25, 2026Material review Sep 25, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=cbc29538dbf7d7400f1ffc5dd5713e6a551463a0 <c4a96da5a3f132d80aa971ddbeb86808539ba0e6 \|\| >=cbc29538dbf7d7400f1ffc5dd5713e6a551463a0 <80b46a3d066d4e2c1dd4edb90d4aa3f22ca79f39 \|\| >=cbc29538dbf7d7400f1ffc5dd5713e6a551463a0 <aa08ce1ffaf36c7bdd3edd0ad65f72413639bfad \|\| >=cbc29538dbf7d7400f1ffc5dd5713e6a551463a0 <e317326d1755ea054b98e7a4833b929157461c35	c4a96da5a3f132d80aa971ddbeb86808539ba0e6, 80b46a3d066d4e2c1dd4edb90d4aa3f22ca79f39, aa08ce1ffaf36c7bdd3edd0ad65f72413639bfad, e317326d1755ea054b98e7a4833b929157461c35
Linux/Linuxgeneric	6.9	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to c4a96da5a3f132d80aa971ddbeb86808539ba0e6 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 25, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.