Zhang Rui

**Name of the Vulnerable Software and Affected Versions** Linux kernel (affected versions not specified) **Description** A segmentation fault issue in the Linux kernel's thermal/netlink component has been resolved. The problem occurred when the intel-lpmd tool, which uses the THERMAL GENL ATTR CPU CAPABILITY attribute, encountered a segmentation fault due to a change in the attribute's raw value. This change was introduced by a commit that added new commands and events for thresholds, affecting existing attributes and potentially causing maintenance burdens for userspace thermal netlink event users. **Recommendations** To resolve the issue, move the newly introduced THERMAL GENL ATTR TZ PREV TEMP attribute to the end of the enum thermal genl attr, ensuring that all existing thermal generic netlink attributes remain unaffected. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

Name of the Vulnerable Software and Affected Versions: Linux kernel (affected versions not specified) Description: A NULL pointer dereference is triggered when probing the MMIO RAPL driver on platforms with CPU ID not listed in intel rapl common CPU model list. This occurs because the intel rapl common module still probes on such platforms even if 'defaults msr' is not set after a specific commit. The MMIO RAPL `rp->priv->defaults` is NULL when registering to the RAPL framework. The issue is resolved by adding a sanity check to ensure `rp->priv->rapl defaults` is always valid. Recommendations: At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Linux kernel (affected versions not specified) **Description** The issue is related to an out-of-bounds memory access in the Linux kernel, specifically in the coretemp module. The problem occurs when the `pdata->cpu map[]` is set before an out-of-bounds check, potentially triggering issues on systems with more than 128 cores per package. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.