CVE-2026-64087
Last modified
CVE-2026-64087 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: hwmon: (pmbus/adm1266) reject implausible blackbox record_count adm1266_nvmem_read_blackbox() loops over a record_count that comes straight from byte 3 of the BLACKBOX_INFO response. The destination buffer is data->dev_mem, sized for the nvmem cell's declared 2048 bytes (ADM1266_BLACKBOX_MAX_RECORDS * ADM1266_BLACKBOX_SIZE = 32 * 64). A device that reports a record_count greater than 32 -- whether due to firmware bugs, bus corruption, or a non-responsive slave returning 0xff -- would walk read_buff past the end of the dev_mem allocation on the trailing iterations. Cap record_count at ADM1266_BLACKBOX_MAX_RECORDS (introduced here) before entering the loop and return -EIO on any larger value, so a malformed BLACKBOX_INFO response cannot drive the loop out of bounds.. EPSS estimates a 0.18% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: hwmon: (pmbus/adm1266) reject implausible blackbox record_count adm1266_nvmem_read_blackbox() loops over a record_count that comes straight from byte 3 of the BLACKBOX_INFO response. The destination buffer is data->dev_mem, sized for the nvmem cell's declared 2048 bytes (ADM1266_BLACKBOX_MAX_RECORDS * ADM1266_BLACKBOX_SIZE = 32 * 64). A device that reports a record_count greater than 32 -- whether due to firmware bugs, bus corruption, or a non-responsive slave returning 0xff -- would walk read_buff past the end of the dev_mem allocation on the trailing iterations. Cap record_count at ADM1266_BLACKBOX_MAX_RECORDS (introduced here) before entering the loop and return -EIO on any larger value, so a malformed BLACKBOX_INFO response cannot drive the loop out of bounds.
Metrics
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 5.10, < 5.10.258 | — |
| Linux | Linux Kernel | >= 5.11, < 5.15.209 | — |
| Linux | Linux Kernel | >= 5.16, < 6.1.175 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.142 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.92 | — |
| Linux | Linux Kernel | >= 6.13, < 6.18.34 | — |
| Linux | Linux Kernel | >= 6.19, < 7.0.11 | — |
| Linux | Linux Kernel | 7.1 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-64087?
How severe is CVE-2026-64087?
How do I fix CVE-2026-64087?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-64081In the Linux kernel, the following vulnerability has been re…8.4
- CVE-2026-64082In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64083In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64084In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64085In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64086In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64088In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-64089In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-6409A Denial of Service (DoS) vulnerability exists in the Protob…7.1
- CVE-2026-64090In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64091In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-64092In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2026-64087?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
