Kernel memory corruption via undersized PMBus buffer
Published Jul 19, 2026 · Updated Jul 19, 2026
Out-of-bounds access in the Linux Kernel ADM1266 PMBus driver allows local users to corrupt kernel memory via a 255-byte block reply. adm1266_pmbus_block_xfer directs 257 bytes into a 256-byte read_buf and then indexes beyond that array during PEC comparison. Reachability requires ADM1266 hardware, control of its I2C reply, and access to a local debugfs or nvmem path; impact includes kernel panic, hang, or code execution.
Summary
What happened
Out-of-bounds access in the Linux Kernel ADM1266 PMBus driver allows local users to corrupt kernel memory via a 255-byte block reply. adm1266_pmbus_block_xfer directs 257 bytes into a 256-byte read_buf and then indexes beyond that array during PEC comparison. Reachability requires ADM1266 hardware, control of its I2C reply, and access to a local debugfs or nvmem path; impact includes kernel panic, hang, or code execution.
The record
- CVE
- CVE-2026-64086
- Published
- Jul 19, 2026
- Updated
- Jul 19, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1068
- Attack vector
- local
- Privileges
- authenticated
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 <2279c342d94eca225bf9f301c8806a05a1c81619
- Affected versionversion=407dc802a9c0809ca6a48de4b4c63305eb84ef56 <397d3f523bfff2f4e3dacf9b1339bd76dc207f78
- Affected versionversion=407dc802a9c0809ca6a48de4b4c63305eb84ef56 <472744f69d25a2d5111ad62f1d62579dce2c13c8
- Affected versionversion=407dc802a9c0809ca6a48de4b4c63305eb84ef56 <487566cb1ccdf3756fdd7bf8d875e612ff3169bb
- Affected versionversion=407dc802a9c0809ca6a48de4b4c63305eb84ef56 <528a9f88e88502d0c2f2052a279415074cd83715
- Affected versionversion=407dc802a9c0809ca6a48de4b4c63305eb84ef56 <a6c802145a8de0830bca803c6d415f7e9e683624
- Affected versionversion=407dc802a9c0809ca6a48de4b4c63305eb84ef56 <bd5be3fa5de6dbf61f1b3cec6b79c2c2f8065694
- Affected versionversion=407dc802a9c0809ca6a48de4b4c63305eb84ef56 <d94ceb16e55b6d8019ab069e357c76ac42f0ffbc
- Affected versionversion=5.10
What conditions does exploitation require?
What is affected?
Published CVSS scores
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