In adm1266_nvmem_read_blackbox() a 5‑byte stack buffer is supplied to i2c_smbus_read_block_data(), which copies up to 32 bytes into the buffer without honoring the original size. If the SMBus device returns a block length larger than five, the memcpy overruns the 5‑byte space before any post‑call validation, potentially corrupting kernel stack data or adjacent memory. The CVE documentation does not document confirmed exploitation; the known impact is kernel memory corruption that could lead to crashes or privilege escalation. Based on the description, it is inferred that the overflow could enable execution of malicious code, but this is not confirmed by any evidence in the report.

All Linux distributions or kernels that ship the adm1266 SMBus driver, irrespective of vendor, and expose the device to SMBus access are susceptible. The vulnerability applies to any kernel version prior to the commit that widens the buffer; specific release identifiers are not listed, so all recent kernels that have not applied the patch are considered vulnerable. Based on the vendor field, the issue is relevant to all Linux distributions that include the adm1266 driver image.

The EPSS score of less than 1 % indicates a very low exploitation probability, and the vulnerability is not listed in the CISA KEV catalog. The described stack overflow could be triggered by a crafted SMBus command, requiring local physical or logical access to the SMBus bus. While no confirmed exploits exist, the potential for kernel memory corruption or privilege escalation exists if an attacker can supply a malicious block length. Remote exploitation is unlikely; the attack vector therefore necessitates local access or elevated privileges to reach the vulnerable driver.