CVE-2025-21952 Details
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
A vulnerability in the Linux kernel's handling of HID Corsair Void devices can cause a kernel panic. The issue arises because the 'corsair_void_process_receiver' function can be called from an interrupt context, and locking the 'battery_mutex' within it was leading to a panic. This vulnerability has been addressed by moving the critical section into a separate work handler, which is shared with 'battery_add_work' and 'battery_remove_work', eliminating the need for locking.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/0c28e4d1e10d2aae608094620bb386e6fd73d55e | kernel.org | Patch |
| https://git.kernel.org/stable/c/de19c9dfb68f7c5791accc89047f92e952f57996 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| NVD-CWE-noinfo | Insufficient Information to Classify Weakness | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 6.13, < 6.13.7 6.14 rc1 6.14 rc2 6.14 rc3 6.14 rc4 6.14 rc5 |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Oct 30, 2025 | Initial Analysis | [email protected] |
| Apr 1, 2025 | New CVE Received | kernel.org |