net: stmmac: initialize ptp_lock at probe time
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ b60189e0392fa06348911077ef281eb2b1047b6a · < b1986595cf827c38ff929e22fbc9ca8f76379306| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net: stmmac: initialize ptp_lock at probe time
priv->ptp_lock is only initialized in stmmac_ptp_register(), which runs during __stmmac_open(). However, the lock is also used while the interface is down and has never been opened: tc_taprio_configure() invokes the PTP gettime64() callback to compute the EST base time when offloading a TAPRIO schedule, and stmmac_get_time() takes priv->ptp_lock. Using an uninitialized rwlock is undefined behaviour. Move the rwlock_init() to __stmmac_dvr_probe(), together with the other private locks, so that ptp_lock is always valid regardless of the interface state.
From the CVE record · Linux
The stmmac driver can use an uninitialized PTP lock when a TAPRIO schedule is offloaded on an interface that is down and has never been opened. This causes undefined behavior; the input does not establish an attacker path, authentication requirement, or user-interaction requirement.
Engineers running Linux kernels with the stmmac driver should check affected versions against the vendor advisory; no versions are listed here.