[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"repo-stars":3,"vuln-DEBIAN-CVE-2025-39937":6},{"stargazers_count":4,"fetched_at":5},7,"2026-06-04T14:53:31.930Z",{"id":7,"descriptions":8,"cisa":9,"weaknesses":10,"exploits":11,"aliases":12,"duplicate_of":9,"upstream":13,"downstream":16,"duplicates":21,"related":22,"reserved_at":9,"published_at":23,"modified_at":24,"state":9,"summary":25,"references_raw":27,"kevs":34,"epss":9,"epss_history":35,"metrics":36,"affected":43},"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",null,[],[],[],[14],{"_key":15},"CVE-2025-39937",[17,19],{"_key":18},"DLA-4379-1",{"_key":20},"DSA-6053-1",[],[],"2025-10-04T08:15:46.593Z","2026-04-28T20:30:23.957533Z",{"cisa_kev":26,"cisa_ransomware":26,"cisa_vendor":9,"epss_severity":9,"epss_score":9,"severity":9,"severity_score":9,"severity_version":9,"severity_source":9,"severity_vector":9,"severity_status":9},false,[28],{"url":29,"sources":30,"tags":32},"https://security-tracker.debian.org/tracker/CVE-2025-39937",[31],"osv_debian",[33],"Advisory",[],[],[37],{"source":31,"cvss_v2_0":9,"cvss_v3_0":9,"cvss_v3_1":38,"cvss_v4_0":9},{"baseScore":39,"baseSeverity":9,"vectorString":40,"impactScore":41,"exploitabilityScore":42},5.5,"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",6,4.6,[44,65],{"ecosystem":45,"name":46,"vendor":47,"product":46,"cpe_part":9,"purl_type":48,"purl_namespace":47,"purl_name":46,"source":9,"versions":49},"Debian","linux","debian","deb",[50,56,59,62],{"version":51,"is_range":52,"range_type":53,"version_start":9,"version_start_type":9,"version_end":54,"version_end_type":55,"fixed_in":9},"lt5_10_247_1",true,"ecosystem","5.10.247-1","excluding",{"version":57,"is_range":52,"range_type":53,"version_start":9,"version_start_type":9,"version_end":58,"version_end_type":55,"fixed_in":9},"lt6_1_158_1","6.1.158-1",{"version":60,"is_range":52,"range_type":53,"version_start":9,"version_start_type":9,"version_end":61,"version_end_type":55,"fixed_in":9},"lt6_12_57_1","6.12.57-1",{"version":63,"is_range":52,"range_type":53,"version_start":9,"version_start_type":9,"version_end":64,"version_end_type":55,"fixed_in":9},"lt6_16_9_1","6.16.9-1",{"ecosystem":45,"name":66,"vendor":47,"product":66,"cpe_part":9,"purl_type":48,"purl_namespace":47,"purl_name":66,"source":9,"versions":67},"linux-6.1",[68],{"version":69,"is_range":52,"range_type":53,"version_start":9,"version_start_type":9,"version_end":70,"version_end_type":55,"fixed_in":9},"lt6_1_158_1~deb11u1","6.1.158-1~deb11u1"]