1. Home
  2. Vulnerabilities
  3. CVE-2025-39937
0.0
NA
CVE-2025-39937
net: rfkill: gpio: Fix crash due to dereferencering uninitialized pointer
Description

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") rfkill_find_type() gets called with the possibly uninitialized "const char *type_name;" local variable. On x86 systems when rfkill-gpio binds to a "BCM4752" or "LNV4752" acpi_device, the rfkill->type is set based on the ACPI acpi_device_id: rfkill->type = (unsigned)id->driver_data; and there is no "type" property so device_property_read_string() will fail and leave type_name uninitialized, leading to a potential crash. rfkill_find_type() does accept a NULL pointer, fix the potential crash by initializing type_name to NULL. Note likely sofar this has not been caught because: 1. Not many x86 machines actually have a "BCM4752"/"LNV4752" acpi_device 2. The stack happened to contain NULL where type_name is stored

INFO

Published Date :

Oct. 4, 2025, 8:15 a.m.

Last Modified :

Oct. 6, 2025, 2:56 p.m.

Remotely Exploit :

No

Source :

416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products

The following products are affected by CVE-2025-39937 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Linux linux_kernel
: Total Affected Vendor : 1 | Products : 1
Solution
Initialize the type_name variable to NULL to prevent potential crashes.
  • Initialize type_name to NULL.
  • Review device property handling.
  • Test affected systems thoroughly.
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2025-39937.

URL Resource
https://git.kernel.org/stable/c/184f608a68f96794e8fe58cd5535014d53622cde
https://git.kernel.org/stable/c/21a39b958b4bcf44f7674bfbbe1bbb8cad0d842d
https://git.kernel.org/stable/c/21ba85d9d508422ca9e6698463ff9357c928c22d
https://git.kernel.org/stable/c/47ade5f9d70b23a119ec20b1c6504864b2543a79
https://git.kernel.org/stable/c/689aee35ce671aab752f159e5c8e66d7685e6887
https://git.kernel.org/stable/c/8793e7a8e1b60131a825457174ed6398111daeb7
https://git.kernel.org/stable/c/ada2282259243387e6b6e89239aeb4897e62f051
https://git.kernel.org/stable/c/b6f56a44e4c1014b08859dcf04ed246500e310e5
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2025-39937 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2025-39937 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2025-39937 vulnerability anywhere in the article.

Results are limited to the first 20 news articles due to potential performance issues.

The following table lists the changes that have been made to the CVE-2025-39937 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Oct. 04, 2025

    Action Type Old Value New Value
    Added Description 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") rfkill_find_type() gets called with the possibly uninitialized "const char *type_name;" local variable. On x86 systems when rfkill-gpio binds to a "BCM4752" or "LNV4752" acpi_device, the rfkill->type is set based on the ACPI acpi_device_id: rfkill->type = (unsigned)id->driver_data; and there is no "type" property so device_property_read_string() will fail and leave type_name uninitialized, leading to a potential crash. rfkill_find_type() does accept a NULL pointer, fix the potential crash by initializing type_name to NULL. Note likely sofar this has not been caught because: 1. Not many x86 machines actually have a "BCM4752"/"LNV4752" acpi_device 2. The stack happened to contain NULL where type_name is stored
    Added Reference https://git.kernel.org/stable/c/184f608a68f96794e8fe58cd5535014d53622cde
    Added Reference https://git.kernel.org/stable/c/21a39b958b4bcf44f7674bfbbe1bbb8cad0d842d
    Added Reference https://git.kernel.org/stable/c/21ba85d9d508422ca9e6698463ff9357c928c22d
    Added Reference https://git.kernel.org/stable/c/47ade5f9d70b23a119ec20b1c6504864b2543a79
    Added Reference https://git.kernel.org/stable/c/689aee35ce671aab752f159e5c8e66d7685e6887
    Added Reference https://git.kernel.org/stable/c/8793e7a8e1b60131a825457174ed6398111daeb7
    Added Reference https://git.kernel.org/stable/c/ada2282259243387e6b6e89239aeb4897e62f051
    Added Reference https://git.kernel.org/stable/c/b6f56a44e4c1014b08859dcf04ed246500e310e5
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.
Vulnerability Scoring Details
No CVSS metrics available for this vulnerability.