The vulnerability allows a kernel use‑after‑free when the amd‑mp2 driver registers an I2C adapter. The driver stores a platform I2C context before the adapter registration succeeds. If i2c_add_adapter() fails, the context is freed, yet the driver’s IRQ and sleep callbacks may still dereference the stale pointer. This stale reference can corrupt kernel memory or cause a crash, potentially allowing an attacker to execute arbitrary code with kernel privileges.

All Linux kernel installations that include the amd‑mp2 PCI driver and I2C subsystem. No specific kernel version is listed in the data, so any kernel containing the affected code path is at risk.

The likely attack vector is a local kernel context where an attacker can load the amd‑mp2 driver and trigger an adapter add that fails, leading to the use‑after‑free. Based on the description, it is inferred that an attacker who can run privileged kernel code could exploit this to gain higher privileges or crash the system. The EPSS score is < 1%, indicating a very low but nonzero probability of exploitation, and the vulnerability is not listed in the CISA KEV catalog. The CVSS score is 7.8, indicating a high severity, and use‑after‑free in the kernel typically leads to memory corruption or arbitrary code execution. The attack path relies on a failed adapter registration, a scenario that can occur during driver initialization or dynamic device probing.