net: stmmac: dwmac-rk: fix oob read in rk_gmac_setup
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 |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net: stmmac: dwmac-rk: fix oob read in rk_gmac_setup
KASAN reports an out-of-bounds read in rk_gmac_setup on the line:
while (ops->regs[i]) {
This happens for most platforms since the regs flexible array member is empty, so the memory after the ops structure is being read here. It seems that mostly this happens to contain zero anyway, so we get lucky and everything still works.
To avoid adding redundant data to nearly all the ops structures, add a new flag to indicate whether the regs field is valid and avoid this loop when it is not.
From the CVE record · Linux
The Linux kernel's dwmac-rk driver can read past the ops structure in rk_gmac_setup when its regs array is empty, as it is on most platforms. The input does not describe an attacker-controlled trigger or specify whether network access, local access, authentication, or user interaction is required.
Engineers running Linux kernels with the dwmac-rk driver should check their kernel versions; affected versions are not specified.