CVE-2025-21952

Medium

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

Package Linux Kernel
Published 2025-04-01
Last modified 2025-10-30
CVSS version 3.1
Patch available
Yes

CVSS 3.1 score

5.5

out of 10
Medium
Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
High
Vector string
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected versions

Linux kernel versions 6.13 and later are affected. Fixed in 6.13.7, 6.14 and their respective stable series.

Affected from
≥ 6.13
Fixed in
✓ 6.13.7 6.13.x ✓ 6.14

References

The following references provide additional information about CVE-2025-21952 including vendor advisories, patch commits, exploit details, and third-party analysis. Links are sourced from the NIST NVD database.

Frequently asked questions

  • What is CVE-2025-21952?

    CVE-2025-21952 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10 . It affects Linux kernel versions from 6.13 onward and has been patched in 6.13.7 and 6.14. CVE-2025-21952 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

  • What is the CVSS score for CVE-2025-21952?

    CVE-2025-21952 has a CVSS score of 5.5 out of 10, rated Medium severity (CVSS 3.1). The vector string is CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H .

  • Is there a patch available for CVE-2025-21952?

    Yes — CVE-2025-21952 has been patched. Fixed versions include 6.13.7 and 6.14. If you are running Linux kernel 6.13 or later up to the fix versions, apply the relevant patch for your kernel branch.

  • Is CVE-2025-21952 actively exploited?

    No — CVE-2025-21952 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.