CVE-2025-39937: Linux kernel · net: rfkill: gpio: Fix crash due to dereferencering uninitialized pointer
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in b6f56a44e4c1014b08859dcf04ed246500e310e5 : update Linux kernel when convenient.
Data as of 5 Nov 2026, 21:34 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-05.
- Patch
- Available – fixed in b6f56a44e4c1014b08859dcf04ed246500e310e5, ada2282259243387e6b6e89239aeb4897e62f051, 8793e7a8e1b60131a825457174ed6398111daeb7 +5
Exploitation evidence
Disclosed: evidence found.
CVE published 4 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
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
References
- git.kernel.org/stable/c/184f608a68f96794e8fe58cd5535014d53622cde (opens in a new tab)
- git.kernel.org/stable/c/8793e7a8e1b60131a825457174ed6398111daeb7 (opens in a new tab)
- git.kernel.org/stable/c/ada2282259243387e6b6e89239aeb4897e62f051 (opens in a new tab)
- git.kernel.org/stable/c/47ade5f9d70b23a119ec20b1c6504864b2543a79 (opens in a new tab)
- git.kernel.org/stable/c/689aee35ce671aab752f159e5c8e66d7685e6887 (opens in a new tab)
- git.kernel.org/stable/c/21ba85d9d508422ca9e6698463ff9357c928c22d (opens in a new tab)
- git.kernel.org/stable/c/21a39b958b4bcf44f7674bfbbe1bbb8cad0d842d (opens in a new tab)
- git.kernel.org/stable/c/b6f56a44e4c1014b08859dcf04ed246500e310e5 (opens in a new tab)