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