Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…
EPSS 0.2%top 93%

In the Linux kernel, the following vulnerability has been resolved: hwmon: (pmbus/adm1266) widen blackbox-info buffer to I2C_SMBUS_BLOCK_MAX… (CVE-2026-64135)

0
Medium
Published: 07/19/2026 (07/19/2026, 18:31:53 UTC)
Source: GCVE Database

Description

A vulnerability in the Linux kernel's hwmon driver for pmbus/adm1266 was resolved by widening a stack buffer used to read SMBus block data. The original code allocated a 5-byte buffer but the SMBus protocol allows up to 32 bytes, which could cause a stack buffer overflow if the device returned more than 5 bytes. This overflow occurs before a length check can reject oversized responses. The fix increases the buffer size to the maximum allowed SMBus block size to prevent overflow.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 07/19/2026, 19:45:47 UTC

Technical Analysis

The Linux kernel hwmon driver for pmbus/adm1266 used a fixed 5-byte stack buffer in adm1266_nvmem_read_blackbox() to read SMBus block data via i2c_smbus_read_block_data(). However, i2c_smbus_read_block_data() copies the number of bytes indicated by the device's length byte, which can be up to I2C_SMBUS_BLOCK_MAX (32 bytes). This mismatch allows a stack buffer overflow if the device returns more than 5 bytes. The vulnerability was resolved by increasing the local buffer size to I2C_SMBUS_BLOCK_MAX, aligning with the SMBus protocol and other driver usage.

Potential Impact

A stack buffer overflow in the Linux kernel hwmon pmbus/adm1266 driver could potentially lead to memory corruption. The description does not specify exploitation details or impact beyond the overflow condition. No known exploits in the wild have been reported.

Mitigation Recommendations

A fix has been implemented in the Linux kernel by widening the buffer to I2C_SMBUS_BLOCK_MAX. Users should update to a kernel version that includes this fix. Since this is a kernel vulnerability, applying the official kernel update or patch that addresses CVE-2026-64135 is the recommended remediation. Patch status is not explicitly confirmed in the provided data; users should verify with the vendor or kernel maintainers for the specific fixed versions.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Gcve Source
db.gcve.eu
Osv Id
GHSA-7g8h-gvx7-vxjc
Osv Schema Version
1.4.0
Aliases
["CVE-2026-64135"]
Ecosystems
[]
Database Specific Severity
null
Cvss Version
null

Threat ID: 6a5d27a82a4a8d598912af16

Added to database: 07/19/2026, 19:38:16 UTC

Last enriched: 07/19/2026, 19:45:47 UTC

Last updated: 07/20/2026, 17:26:47 UTC

Views: 12

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses