{"apiVersion":"1.0","identifier":"CVE-2026-74711","description":"In the Linux kernel, the following vulnerability has been resolved: hwmon: (pmbus) Fix type confusion in notification logic Sashiko reports: At the start of the loop in pmbus_notify(), the code unconditionally casts every attribute to a struct sensor_device_attribute: drivers/hwmon/pmbus/pmbus_core.c:pmbus_notify() { for (i = 0; i < data->num_attributes; i++) { struct device_attribute *da = to_dev_attr(data->group.attrs[i]); struct sensor_device_attribute *attr = to_sensor_dev_attr(da); int index = attr->index; ... } However, data->group.attrs can contain other types like struct pmbus_samples_reg or struct pmbus_sensor, which only embed a base struct device_attribute. If da is a struct pmbus_samples_reg, dev_attr is the last member. Casting it to struct sensor_device_attribute and reading the index field appears to access memory past the end of the allocation, which might trigger a slab-out-of-bounds read. Additionally, if da is a struct pmbus_sensor, casting it causes the index field to overlap with the page, phase, and reg fields. Could this produce a garbage mask on little-endian systems that spuriously matches the target reg, page, and flags during an alert? Fix the problem by using struct sensor_device_attr in struct pmbus_sensor and struct pmbus_label. Since those attributes never trigger a notification, set the value of attr->index to -1 for them. Use this value to distinguish from boolean attributes which _can_ trigger a notification and use the index field to encode mask, page, and register values.","publishedAt":"2026-08-22T16:16:45","lastModifiedAt":"2026-08-25T06:18:55","sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2026-74711","cvssScore":8.4,"cvssVector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","epssProbability":0.0014,"riskScore":0.85,"affectedProduct":"Linux kernel","affectedVersions":"unknown","vulnerabilityType":"Kernel","operatingSystems":[],"links":{"self":"https://www.redsauce.net/api/cves/CVE-2026-74711","webPages":{"es":"https://www.redsauce.net/es/cves/CVE-2026-74711","en":"https://www.redsauce.net/en/cves/CVE-2026-74711","fr":"https://www.redsauce.net/fr/cves/CVE-2026-74711","pt":"https://www.redsauce.net/pt/cves/CVE-2026-74711","de":"https://www.redsauce.net/de/cves/CVE-2026-74711","sk":"https://www.redsauce.net/sk/cves/CVE-2026-74711","el":"https://www.redsauce.net/el/cves/CVE-2026-74711"},"source":"https://nvd.nist.gov/vuln/detail/CVE-2026-74711"}}