net: dsa: realtek: fix out-of-bounds access
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.1.236.2.106.3In 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.
From the CVE record · Linux
The Linux kernel’s Realtek MDIO driver can access memory out of bounds during device probing because it does not allocate space for chip data. This can cause memory corruption, particularly with a different allocator or KASAN; the input does not establish an attack path, authentication requirements, or user interaction.
Engineers running Linux kernels with the Realtek MDIO driver should check their deployments; affected versions are not specified.