Input: uinput - fix circular locking dependency with ff-core
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ ff462551235d8d7d843a005950bc90924fcedede · < 1e09dfbb4f5d20ee111f92325a00f85778a5f328| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
Input: uinput - fix circular locking dependency with ff-core
A lockdep circular locking dependency warning can be triggered reproducibly when using a force-feedback gamepad with uinput (for example, playing ELDEN RING under Wine with a Flydigi Vader 5 controller):
ff->mutex -> udev->mutex -> input_mutex -> dev->mutex -> ff->mutex
The cycle is caused by four lock acquisition paths:
1. ff upload: input_ff_upload() holds ff->mutex and calls uinput_dev_upload_effect() -> uinput_request_submit() -> uinput_request_send(), which acquires udev->mutex.
2. device create: uinput_ioctl_handler() holds udev->mutex and calls uinput_create_device() -> input_register_device(), which acquires input_mutex.
3. device register: input_register_device() holds input_mutex and calls kbd_connect() -> input_register_handle(), which acquires dev->mutex.
From the CVE record · Linux
The Linux kernel's uinput force-feedback path has a circular locking dependency. Using a force-feedback gamepad with uinput can reproducibly trigger a lockdep warning; the input does not specify authentication requirements or an attacker-controlled exploit path.
Engineers running the Linux kernel with uinput and force-feedback devices should check their kernel; affected versions are not specified.