CVE-2026-74711hwmon: (pmbus) Fix type confusion in notification logic
- 8.4HighCVSS base score
- 0.14%Exploitation in 30 daysEPSS · top 96% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 7 days later
· 7 days later
Published
- 2 months later
· 2 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High8.4 | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Received | 3.1 | High8.4 | CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.14% · top 96% of all CVEs (17 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.4.
Affected products
- affected f469bde9afd136598a0c4edc054296e6046f90ee – < ce443f6827b97e03a0fb34ebfddc8939c85e0500
- affected f469bde9afd136598a0c4edc054296e6046f90ee – < 1c8dd39d48494cceb2c27c1911cbf26d10ce8514
- affected f469bde9afd136598a0c4edc054296e6046f90ee – < 821f6416e69782fa662aff94b5ea52c943042790
- affected f469bde9afd136598a0c4edc054296e6046f90ee – < 0b121de89a99c54bcf516999b04e8531c84f08d5
- affected f469bde9afd136598a0c4edc054296e6046f90ee – < 59bd68ab05a8f9c9a60b6ec44682084184803ff4
- affected 6.4
- unaffected < 6.4
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.114 – ≤ 6.12.*
- unaffected 6.18.45 – ≤ 6.18.*
- unaffected 7.1.9 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References5
- https://git.kernel.org/stable/c/ce443f6827b97e03a0fb34ebfddc8939c85e0500 (opens in a new tab)
- https://git.kernel.org/stable/c/1c8dd39d48494cceb2c27c1911cbf26d10ce8514 (opens in a new tab)
- https://git.kernel.org/stable/c/821f6416e69782fa662aff94b5ea52c943042790 (opens in a new tab)
- https://git.kernel.org/stable/c/0b121de89a99c54bcf516999b04e8531c84f08d5 (opens in a new tab)
- https://git.kernel.org/stable/c/59bd68ab05a8f9c9a60b6ec44682084184803ff4 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-64398 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-74711)Record last updated .