hwmon: (coretemp) Set nr_cores only after core_data allocation succeeds
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 2fb99a03cb8c4a5907c55968d1aa8df6c885e347, Kernel 95638f1f05ced75a82e83f610cd01b636d2a21b1 and Kernel 7.3.5.
In the Linux kernel, the following vulnerability has been resolved: hwmon: (coretemp) Set nr_cores only after core_data allocation succeeds In init_temp_data(), pdata->nr_cores is populated from topology_num_cores_per_package() before allocating pdata->core_data. If that allocation fails, init_temp_data() returns NULL with pdata->core_data still NULL and pdata->nr_cores set to a positive value. coretemp_add_core() logs the error without failing coretemp_cpu_online(), so the CPU still comes online with pdata->hwmon_dev registered. When the CPU is later taken offline (or the module is unloaded), coretemp_cpu_offline() calls get_temp_data(pd, cpu), which loops up to pdata->nr_cores and dereferences the NULL pdata->core_data pointer. Store the core count in a local variable and assign pdata->nr_cores only after pdata->core_data is allocated, preserving the invariant that pdata->nr_cores is zero whenever pdata->core_data is NULL.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.9, >=1a793caf6f6991716cb07583ed7c27de84ef0cba <2fb99a03cb8c4a5907c55968d1aa8df6c885e347, >=1a793caf6f6991716cb07583ed7c27de84ef0cba <95638f1f05ced75a82e83f610cd01b636d2a21b1 | 2fb99a03cb8c4a5907c55968d1aa8df6c885e347, 95638f1f05ced75a82e83f610cd01b636d2a21b1 |
| linux-kernel: Kernel | >=6.9.0 <7.3.5 | 7.3.5 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket