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
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.13.7
- CVEs
- CVE-2025-21952
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 00:44 UTC · Revision 1
Source evidence
HID: corsair-void: Update power supply values with a unified work handler
core-osv · Original sourcePublished 1 Apr 2025, 15:41 UTC
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
osv:CVE-2025-21952
Kernel
Fixed versions: 6.13.7
Complete source record
{
"id": "92aade59f34e7b536f1010ebffc2ee4bea563e4c25a9ca144b682414e5149074",
"url": "https://osv.dev/vulnerability/CVE-2025-21952",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "HID: corsair-void: Update power supply values with a unified work handler",
"summary": "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",
"evidence": "osv:CVE-2025-21952",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.13.7",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2025-21952",
"aliases": [
"CVE-2025-21952"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "6ea2a6fd3872e60a4d500b548ad65ed94e459ddd"
},
{
"fixed": "de19c9dfb68f7c5791accc89047f92e952f57996"
},
{
"fixed": "0c28e4d1e10d2aae608094620bb386e6fd73d55e"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-21952.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.13.7"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-21952.json"
}
}
],
"modified": "2026-10-28T02:30:24.936610812Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/0c28e4d1e10d2aae608094620bb386e6fd73d55e",
"https://git.kernel.org/stable/c/de19c9dfb68f7c5791accc89047f92e952f57996",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/21xxx/CVE-2025-21952.json",
"https://nvd.nist.gov/vuln/detail/CVE-2025-21952",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/21xxx/CVE-2025-21952.json"
}
},
"related_cves": [
{
"value": "CVE-2025-21952",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 491296,
"published_at": "2025-04-01T15:41:12.024+00:00"
}