CVE-2022-48632 is a stack-based buffer overflow in the Linux kernel Mellanox BlueField MLXBF I2C driver. In mlxbf_i2c_smbus_start_transaction(), memcpy() operations are performed in a loop without enforcing an upper bound on operation->length while the destination index advances. An oversized operation length can consequently cause copying beyond a stack-allocated buffer. The flaw was introduced in Linux kernel 5.10 and is fixed upstream in 5.10.146, 5.15.71, 5.19.12, and 6.0.
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.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel stack-overflow vulnerability in the mlxbf I2C driver function mlxbf_i2c_smbus_start_transaction().
A Linux kernel stack-overflow flaw in the Mellanox BlueField I2C (i2c-mlxbf) driver's SMBus transaction handling. Red Hat assesses its impact as availability-only for its builds, potentially causing a system crash or denial of service.
A Linux kernel stack-overflow vulnerability in the MLXBF I2C bus driver. An unchecked operation->length value allows repeated memcpy() operations while data_idx increments in mlxbf_i2c_smbus_start_transaction().
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.