DEBIAN-CVE-2025-39937
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
Risk Scores
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Debian:12 | linux | 0, 6.1.55-1, 6.1.64-1 |
| Debian:11 | linux | 5.10.84-1, *, 0 |
| Debian:11 | linux-6.1 | 6.1.153-1~deb11u1, 0, 6.1.106-3 |
| Debian:13 | linux | 6.12.38-1, 6.12.43-1~bpo12+1, 6.12.48-1 |
| Debian:14 | linux | 6.12.74-2, 6.12.74-1, 6.12.73-1 |
Timeline
- Oct 4, 2025 CVE Published
- Apr 28, 2026 CVE Updated