CVE-2025-21952: HID: corsair-void: Update power supply values with a unified work handler
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
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can crash a machine when Corsair Void headset receiver handling updates battery or power information incorrectly. It is an availability risk, not a confirmed data theft path. Business urgency depends on whether affected Linux kernels and the corsair-void HID driver/device path are present.
Executive priority
Treat as a targeted stability issue. Patch through normal kernel maintenance, faster where Linux desktops, kiosks, or operational endpoints use the affected Corsair receiver path. There is no source evidence of active exploitation or broader remote compromise.
Technical view
The CVE describes a kernel panic caused when corsair_void_process_receiver, which can execute in interrupt context, locks battery_mutex. The upstream fix moves the critical section into a unified work handler shared with battery add and remove work, avoiding the unsafe locking pattern.
Likely exposure
Most exposure is likely on Linux systems running affected 6.13-era kernels with Corsair Void HID receiver support in use. Servers are less likely exposed unless this hardware or driver path is present. Source version data is sparse and should be verified against distribution advisories.
Exploitation context
The provided sources do not report active exploitation, public weaponization, or KEV listing. The documented impact is kernel panic, suggesting denial of service through a driver execution path. Required attacker position and trigger conditions are not fully described in the source bundle.
Researcher notes
The source bundle provides the root cause and fix direction but no CVSS, CWE, detailed affected range, or exploit prerequisites. Avoid assuming remote reachability. Validate downstream backports because Linux distributions may carry the fix under different package versions.
Mitigation direction
Check vendor or distribution advisories for patched kernel packages.
Upgrade to a kernel containing the referenced stable fixes.
Prioritize systems using Corsair Void receivers or the corsair-void HID driver.
If upgrade is delayed, assess whether the affected hardware or driver can be removed.
Validation and detection
Inventory Linux kernel versions against vendor advisories for CVE-2025-21952.
Check whether corsair-void HID support is present or loaded.
Review endpoint hardware inventories for Corsair Void receivers.
Confirm installed kernel includes the linked stable commits or downstream backport.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-21952 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
3Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Apr 1, 2025, 15:41 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.