| From bippy-7c5fe7eed585 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@linuxfoundation.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2025-21952: HID: corsair-void: Update power supply values with a unified work handler |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| HID: corsair-void: Update power supply values with a unified work handler |
| |
| corsair_void_process_receiver can be called from an interrupt context, |
| locking battery_mutex in it was causing a kernel panic. |
| Fix it by moving the critical section into its own work, sharing this |
| work with battery_add_work and battery_remove_work to remove the need |
| for any locking |
| |
| The Linux kernel CVE team has assigned CVE-2025-21952 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 6.13 with commit 6ea2a6fd3872e60a4d500b548ad65ed94e459ddd and fixed in 6.13.7 with commit de19c9dfb68f7c5791accc89047f92e952f57996 |
| Issue introduced in 6.13 with commit 6ea2a6fd3872e60a4d500b548ad65ed94e459ddd and fixed in 6.14 with commit 0c28e4d1e10d2aae608094620bb386e6fd73d55e |
| |
| Please see https://www.kernel.org for a full list of currently supported |
| kernel versions by the kernel community. |
| |
| Unaffected versions might change over time as fixes are backported to |
| older supported kernel versions. The official CVE entry at |
| https://cve.org/CVERecord/?id=CVE-2025-21952 |
| will be updated if fixes are backported, please check that for the most |
| up to date information about this issue. |
| |
| |
| Affected files |
| ============== |
| |
| The file(s) affected by this issue are: |
| drivers/hid/hid-corsair-void.c |
| |
| |
| Mitigation |
| ========== |
| |
| The Linux kernel CVE team recommends that you update to the latest |
| stable kernel version for this, and many other bugfixes. Individual |
| changes are never tested alone, but rather are part of a larger kernel |
| release. Cherry-picking individual commits is not recommended or |
| supported by the Linux kernel community at all. If however, updating to |
| the latest release is impossible, the individual changes to resolve this |
| issue can be found at these commits: |
| https://git.kernel.org/stable/c/de19c9dfb68f7c5791accc89047f92e952f57996 |
| https://git.kernel.org/stable/c/0c28e4d1e10d2aae608094620bb386e6fd73d55e |