Independent & educational platform Not a government body. No link or affiliation with any government organisation. Made for learning only. Test only systems you own or are authorised to test. Become a Partner or Sponsor → Full disclaimer

CVE-2025-39937

medium

In the Linux kernel, the following vulnerability has been resolved: net: rfkill: gpio: Fix crash due to dereferencering uninitialized pointer Since commit 7d…

Vendor / product: Linux — linux kernel

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
5.5 (CVSS v3.1)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Severity source: NVD CVSS v3.1 (nvd@nist.gov)
Timeline (UTC)
Published: 2025-10-04 08:15
Modified: 2026-11-05 22:17
NVD status: Analyzed
Last synced 1 week ago
Verified against the source API 2026-11-05 22:23 UTC
Exploitation
Not listed in CISA KEV (as of last catalog sync)
Absence from KEV does not mean a CVE is not exploited. Exploitation status: unknown (no authoritative evidence in our sources).

Affected products

linux / linux_kernel ≥4.6 <5.4.300, ≥5.5 <5.10.245, ≥5.11 <5.15.194, ≥5.16 <6.1.154, ≥6.2 <6.6.108, ≥6.7 <6.12.49

Weakness classification (CWE)

Source: NVD / CISA. “NVD-CWE-Other” and “NVD-CWE-noinfo” mean NVD could not assign a specific weakness.

Mitigation & advisories

Patch / mitigation: https://git.kernel.org/stable/c/184f608a68f96794e8fe58cd5535014d53622cde
Patch / mitigation: https://git.kernel.org/stable/c/21a39b958b4bcf44f7674bfbbe1bbb8cad0d842d
Patch / mitigation: https://git.kernel.org/stable/c/21ba85d9d508422ca9e6698463ff9357c928c22d
Patch / mitigation: https://git.kernel.org/stable/c/47ade5f9d70b23a119ec20b1c6504864b2543a79
Patch / mitigation: https://git.kernel.org/stable/c/689aee35ce671aab752f159e5c8e66d7685e6887
Patch / mitigation: https://git.kernel.org/stable/c/8793e7a8e1b60131a825457174ed6398111daeb7
Patch / mitigation: https://git.kernel.org/stable/c/ada2282259243387e6b6e89239aeb4897e62f051
Patch / mitigation: https://git.kernel.org/stable/c/b6f56a44e4c1014b08859dcf04ed246500e310e5

References

Data sources

NVD CVE API 2.0 — fetched 2026-11-05 22:23 UTC · record ↗

Learn the basics

Understanding CVEs and CVSS Scores

Related CVEs