Local kernel crash via uninitialized rfkill type pointer
Published Oct 4, 2025 · Updated Oct 4, 2025
NULL pointer dereference in the Linux kernel allows local users to crash affected x86 systems during rfkill-gpio device binding. A failed device_property_read_string call leaves type_name uninitialized, and rfkill_find_type then consumes the invalid pointer. Reachability requires a BCM4752 or LNV4752 ACPI device without a type property; the reported consequence is a kernel crash without data disclosure or modification.
Summary
What happened
NULL pointer dereference in the Linux kernel allows local users to crash affected x86 systems during rfkill-gpio device binding. A failed device_property_read_string call leaves type_name uninitialized, and rfkill_find_type then consumes the invalid pointer. Reachability requires a BCM4752 or LNV4752 ACPI device without a type property; the reported consequence is a kernel crash without data disclosure or modification.
The record
- CVE
- CVE-2025-39937
- Published
- Oct 4, 2025
- Updated
- Oct 4, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 4, 2025CVE publishedPublication date reported by the CVE source.
- Oct 4, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.6
- Affected versionversion=7d5e9737efda16535e5b54bd627ef4881d11d31f <184f608a68f96794e8fe58cd5535014d53622cde
- Affected versionversion=7d5e9737efda16535e5b54bd627ef4881d11d31f <21a39b958b4bcf44f7674bfbbe1bbb8cad0d842d
- Affected versionversion=7d5e9737efda16535e5b54bd627ef4881d11d31f <21ba85d9d508422ca9e6698463ff9357c928c22d
- Affected versionversion=7d5e9737efda16535e5b54bd627ef4881d11d31f <47ade5f9d70b23a119ec20b1c6504864b2543a79
- Affected versionversion=7d5e9737efda16535e5b54bd627ef4881d11d31f <689aee35ce671aab752f159e5c8e66d7685e6887
- Affected versionversion=7d5e9737efda16535e5b54bd627ef4881d11d31f <8793e7a8e1b60131a825457174ed6398111daeb7
- Affected versionversion=7d5e9737efda16535e5b54bd627ef4881d11d31f <ada2282259243387e6b6e89239aeb4897e62f051
- Affected versionversion=7d5e9737efda16535e5b54bd627ef4881d11d31f <b6f56a44e4c1014b08859dcf04ed246500e310e5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo