dpll: zl3073x: use __dpll_device_change_ntf() and remove change_work
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:
dpll: zl3073x: use __dpll_device_change_ntf() and remove change_work
The change_work was introduced to send device change notifications from DPLL device callbacks without deadlocking on dpll_lock, since the callbacks are already invoked under that lock. Now that __dpll_device_change_ntf() is exported for callers that already hold dpll_lock, use it directly and remove the change_work infrastructure entirely.
This eliminates a race condition where change_work could be re-scheduled after cancel_work_sync() during device teardown, potentially causing the handler to dereference a freed or NULL dpll_dev pointer.
From the CVE record · Linux
The Linux kernel’s zl3073x DPLL driver has a race during device teardown. A change-notification worker can be rescheduled after cancellation and dereference a freed or NULL pointer, potentially causing a crash. The input does not establish whether an attacker can trigger this or what access would be required.
Engineers running Linux kernels with the zl3073x DPLL driver should check their versions; affected versions were not provided.