e1000e: change usleep_range to udelay in PHY mdic 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 |
|
In the Linux kernel, the following vulnerability has been resolved:
e1000e: change usleep_range to udelay in PHY mdic access
This is a partial revert of commit 6dbdd4de0362 ("e1000e: Workaround for sporadic MDI error on Meteor Lake systems"). The referenced commit used usleep_range inside the PHY access routines, which are sometimes called from an atomic context. This can lead to a kernel panic in some scenarios, such as cable disconnection and reconnection on vPro systems.
Solve this by changing the usleep_range calls back to udelay.
From the CVE record · Linux
The Linux kernel e1000e driver can call a sleeping delay from PHY access routines running in an atomic context. This can cause a kernel panic in scenarios such as disconnecting and reconnecting a cable on a vPro system. The input does not specify an attacker access or authentication requirement.
Operators of Linux systems using the e1000e driver should check their kernel versions; affected versions are not specified.