Input: byd - synchronize timer deletion before freeing private data
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 2d5f5611dd0de52e9a52b56391a7049a52184e72 · < 8dbfd8e32a13e116790780ed0be82b5a05eb9916| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
Input: byd - synchronize timer deletion before freeing private data
byd_disconnect() uses timer_delete() before freeing the driver's private data. This does not wait for a running byd_clear_touch() callback, which dereferences the private data and its psmouse pointer. A callback racing with disconnect can therefore access the private data after it has been freed. The timer can also still be re-armed by byd_process_byte() while the disconnect is in progress.
Use timer_shutdown_sync() before freeing the private data: it waits for a running callback and turns any later re-arm attempt into a no-op.
From the CVE record · Linux
The Linux kernel’s byd input driver can free private data while a timer callback is still using it. A race during device disconnect can cause a use-after-free; the input does not specify attacker access or user-interaction requirements.
Engineers running Linux kernels with the byd input driver should check whether their kernel includes the fix; affected versions were not specified.