CVE-2025-39937In 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 na…
Updated under an hour ago ()
Does this affect you?
It affects linux_kernel. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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
- CVSS
- 5.5 MEDIUM (v3.1, NVD)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- Weakness (CWE)
- CWE-476
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Not given
- NVD analysis
- Analyzed
- Record last updated
- Oct 19, 2026
- First seen by InfoSec Signals
- Oct 19, 2026
Affected products
linux linux_kernel linux:linux_kernel | from 4.6 before 5.4.300; from 5.5 before 5.10.245; from 5.11 before 5.15.194; from 5.16 before 6.1.154; from 6.2 before 6.6.108; from 6.7 before 6.12.49; from 6.13 before 6.16.9; 6.17; and 5 more ranges | NVD |
References
- https://git.kernel.org/stable/c/184f608a68f96794e8fe58cd5535014d53622cdepatch
- https://git.kernel.org/stable/c/21a39b958b4bcf44f7674bfbbe1bbb8cad0d842dpatch
- https://git.kernel.org/stable/c/21ba85d9d508422ca9e6698463ff9357c928c22dpatch
- https://git.kernel.org/stable/c/47ade5f9d70b23a119ec20b1c6504864b2543a79patch
- https://git.kernel.org/stable/c/689aee35ce671aab752f159e5c8e66d7685e6887patch
- https://git.kernel.org/stable/c/8793e7a8e1b60131a825457174ed6398111daeb7patch
- https://git.kernel.org/stable/c/ada2282259243387e6b6e89239aeb4897e62f051patch
- https://git.kernel.org/stable/c/b6f56a44e4c1014b08859dcf04ed246500e310e5patch
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.