CVE-2025-39937: net: rfkill: gpio: Fix crash due to dereferencering uninitialized pointer
In the Linux kernel, the following vulnerability has been resolved:
net: rfkill: gpio: Fix crash due to dereferencering uninitialized pointer
Since commit 7d5e9737efda ("net: rfkill: gpio: get the name and type from device property") rfkillfindtype() gets called with the possibly uninitialized "const char typename;" local variable.
On x86 systems when rfkill-gpio binds to a "BCM4752" or "LNV4752" acpidevice, the rfkill->type is set based on the ACPI acpideviceid:
rfkill->type = (unsigned)id->driverdata;
and there is no "type" property so devicepropertyreadstring() will fail and leave typename uninitialized, leading to a potential crash.
rfkillfindtype() does accept a NULL pointer, fix the potential crash by initializing typename to NULL.
Note likely sofar this has not been caught because:
1. Not many x86 machines actually have a "BCM4752"/"LNV4752" acpidevice 2. The stack happened to contain NULL where typename is stored
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2025-39937?
CVE-2025-39937 has a high severity rating due to the potential for system crashes.
How do I fix CVE-2025-39937?
To fix CVE-2025-39937, update your Linux kernel to the latest stable version where the vulnerability is addressed.
What systems are affected by CVE-2025-39937?
CVE-2025-39937 affects various versions of the Linux kernel that include the rfkill component.
What are the potential impacts of CVE-2025-39937?
The potential impacts of CVE-2025-39937 include system crashes and degraded system stability.
Is CVE-2025-39937 exploitable remotely?
CVE-2025-39937 is not typically considered exploitable remotely, as it requires local access to the kernel.