Description

In the Linux kernel, the following vulnerability has been resolved: net: dsa: realtek: fix out-of-bounds access The probe function sets priv->chip_data to (void *)priv + sizeof(*priv) with the expectation that priv has enough trailing space. However, only realtek-smi actually allocated this chip_data space. Do likewise in realtek-mdio to fix out-of-bounds accesses. These accesses likely went unnoticed so far, because of an (unused) buf[4096] member in struct realtek_priv, which caused kmalloc to round up the allocated buffer to a big enough size, so nothing of value was overwritten. With a different allocator (like in the barebox bootloader port of the driver) or with KASAN, the memory corruption becomes quickly apparent.

References 3

• git.kernel.org https://git.kernel.org/stable/c/b93eb564869321d0dffaf23fcc5c88112ed62466
• git.kernel.org https://git.kernel.org/stable/c/cc0f9bb99735d2b68fac68f37b585d615728ce5b
• git.kernel.org https://git.kernel.org/stable/c/fe668aa499b4b95425044ba11af9609db6ecf466

Remediation