Kernel memory corruption via oversized blackbox record
Published Jul 19, 2026 · Updated Jul 19, 2026
An out-of-bounds write in the Linux kernel ADM1266 hwmon driver allows local users to corrupt kernel memory through a long blackbox response. adm1266_pmbus_block_xfer() trusts the device-supplied byte count and writes as many as 255 bytes into a 64-byte dev_mem record slot before adm1266_nvmem_read_blackbox() rejects the length. Reachability requires local access and an ADM1266 chip; published sources characterize no outcome beyond kernel-memory corruption.
Summary
What happened
An out-of-bounds write in the Linux kernel ADM1266 hwmon driver allows local users to corrupt kernel memory through a long blackbox response. adm1266_pmbus_block_xfer() trusts the device-supplied byte count and writes as many as 255 bytes into a 64-byte dev_mem record slot before adm1266_nvmem_read_blackbox() rejects the length. Reachability requires local access and an ADM1266 chip; published sources characterize no outcome beyond kernel-memory corruption.
The record
- CVE
- CVE-2026-64085
- Published
- Jul 19, 2026
- Updated
- Jul 19, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-120
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Jul 19, 2026CVE publishedPublication date reported by the CVE source.
- Jul 19, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=407dc802a9c0809ca6a48de4b4c63305eb84ef56 <43cae21424ff8e33894a0f86c6b80b840c049fd7
- Affected versionversion=407dc802a9c0809ca6a48de4b4c63305eb84ef56 <6098634cfa711f11a8d65368dc51ec8f7c8241ba
- Affected versionversion=407dc802a9c0809ca6a48de4b4c63305eb84ef56 <60c4b9fe1a3dd012014b1f561a6928a0b5db1126
- Affected versionversion=407dc802a9c0809ca6a48de4b4c63305eb84ef56 <7896d87cbb05e097efc113243d4e38f9f8cea16c
- Affected versionversion=407dc802a9c0809ca6a48de4b4c63305eb84ef56 <83e039f0a43e0708515b0479cb7690fb93faaaa0
- Affected versionversion=407dc802a9c0809ca6a48de4b4c63305eb84ef56 <97a9cf2a8217ca1cdaf48cb9ab26e471632c7e7f
- Affected versionversion=407dc802a9c0809ca6a48de4b4c63305eb84ef56 <9d5309500b4607b7198e19f0a3fa13eb864cd5fb
- Affected versionversion=407dc802a9c0809ca6a48de4b4c63305eb84ef56 <dd47b8c4a0a8ced442da3f008db28fbbd31feaf0
- Affected versionversion=5.10
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo