Loading vulnerability…
CVE-2026-64191 is an out-of-bounds memory-access vulnerability in the Linux kernel I2C stub development/test driver. In the I2C_SMBUS_I2C_BLOCK_DATA path of stub_xfer(), the driver uses the user-controlled block-length byte as a transfer length but only constrains it relative to its emulated register array; it does not enforce the 32-byte I2C_SMBUS_BLOCK_MAX limit of the SMBus data buffer. Because the driver implements its SMBus transfer callback directly, it bypasses validation available in the emulated transfer path. The flaw permits reads or writes beyond the SMBus block buffer when an oversized length is supplied. The fix rejects zero-length and lengths exceeding I2C_SMBUS_BLOCK_MAX with -EINVAL.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
14 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability addressed by the Oracle Linux 9 kernel security update.
A vulnerability referenced in the Oracle Linux 8 kernel-related security advisory; no technical flaw details are provided.
Linux kernel I2C stub driver flaw involving acceptance of I2C block transfers with invalid lengths.
Linux kernel I2C stub flaw involving acceptance of I2C block transfers with invalid lengths.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.