net/mdiobus: Fix potential out-of-bounds read/write access
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 080bb352fad00d04995102f681b134e3754bfb6e · < 049af7ac45a6b407748ee0995278fd861e36df8f| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net/mdiobus: Fix potential out-of-bounds read/write access
When using publicly available tools like 'mdio-tools' to read/write data from/to network interface and its PHY via mdiobus, there is no verification of parameters passed to the ioctl and it accepts any mdio address. Currently there is support for 32 addresses in kernel via PHY_MAX_ADDR define, but it is possible to pass higher value than that via ioctl. While read/write operation should generally fail in this case, mdiobus provides stats array, where wrong address may allow out-of-bounds read/write.
Fix that by adding address verification before read/write operation. While this excludes this access from any statistics, it improves security of read/write operation.
From the CVE record · Linux
The Linux kernel’s mdiobus ioctl does not validate MDIO addresses before read and write operations. A local user able to issue the ioctl can supply an address beyond the 32 supported addresses, potentially causing an out-of-bounds read or write in the statistics array. The input does not specify an authentication requirement or user interaction.
Engineers running Linux kernels with the affected net/mdiobus code should check their versions; affected versions were not provided.