CVE-2025-39937

Medium

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

SeverityMedium
CVSS5.5
Exploit probability—
ProductLinux Kernel
PublishedOct 4, 2025
First seenOct 4, 2025

How to fix

Affected products

ProductAffected versionsFixed in
linux linux_kernel4.6 ≤ v < 5.4.300, 5.5 ≤ v < 5.10.245, 5.11 ≤ v < 5.15.194, 5.16 ≤ v < 6.1.154, 6.2 ≤ v < 6.6.108, 6.7 ≤ v < 6.12.49, 6.13 ≤ v < 6.16.9, 6.175.4.300, 5.10.245, 5.15.194, 6.1.154, 6.6.108, 6.12.49, 6.16.9

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.