net: mdio: unexport __init-annotated mdio_bus_init()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 90eff9096c01ba90cdae504a6b95ee87fe2556a3 · < f5c68137f1191ba3fcf6260ec71b30be2e2bf4c3| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net: mdio: unexport __init-annotated mdio_bus_init()
EXPORT_SYMBOL and __init is a bad combination because the .init.text section is freed up after the initialization. Hence, modules cannot use symbols annotated __init. The access to a freed symbol may end up with kernel panic.
modpost used to detect it, but it has been broken for a decade.
Recently, I fixed modpost so it started to warn it again, then this showed up in linux-next builds.
There are two ways to fix it:
- Remove __init - Remove EXPORT_SYMBOL
I chose the latter for this case because the only in-tree call-site, drivers/net/phy/phy_device.c is never compiled as modular. (CONFIG_PHYLIB is boolean)
From the CVE record · Linux
The Linux kernel exports an MDIO bus initialization function from a section freed after initialization. A module accessing that function may cause a kernel panic. The input does not describe an attacker path or specify access or user-interaction requirements.
Engineers running Linux kernels with the affected MDIO code should check their deployments; affected versions are not specified.