net: phy: fix phy_get_internal_delay accessing an empty array
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 92252eec913b2dd5e7b5de11ea3efa2e64d65cf4 · < 0307cf443308ecc6be9b2ca312bb31bae5e5a7ad| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net: phy: fix phy_get_internal_delay accessing an empty array
The phy_get_internal_delay function could try to access to an empty array in the case that the driver is calling phy_get_internal_delay without defining delay_values and rx-internal-delay-ps or tx-internal-delay-ps is defined to 0 in the device-tree. This will lead to "unable to handle kernel NULL pointer dereference at virtual address 0". To avoid this kernel oops, the test should be delay >= 0. As there is already delay < 0 test just before, the test could only be size == 0.
From the CVE record · Linux
The Linux kernel’s phy_get_internal_delay function can access an empty array when a driver defines no delay_values and a device-tree RX or TX internal delay is set to zero. This causes a kernel NULL pointer dereference and oops. The input does not establish whether an attacker can trigger it or whether authentication or user interaction is required.
Engineers running Linux kernels whose PHY drivers call phy_get_internal_delay should check their device-tree configuration; affected versions are not specified.