Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-39937net: rfkill: gpio: Fix crash due to dereferencering uninitialized pointer

Description

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

Timeline

  1. ID reserved

    By Linux

  2. · 6 months later

    Published

  3. · 13 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-39937, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.15% · top 96% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 7d5e9737efda16535e5b54bd627ef4881d11d31f – < 184f608a68f96794e8fe58cd5535014d53622cde
    • affected 7d5e9737efda16535e5b54bd627ef4881d11d31f – < 8793e7a8e1b60131a825457174ed6398111daeb7
    • affected 7d5e9737efda16535e5b54bd627ef4881d11d31f – < ada2282259243387e6b6e89239aeb4897e62f051
    • affected 7d5e9737efda16535e5b54bd627ef4881d11d31f – < 47ade5f9d70b23a119ec20b1c6504864b2543a79
    • affected 7d5e9737efda16535e5b54bd627ef4881d11d31f – < 689aee35ce671aab752f159e5c8e66d7685e6887
    • affected 7d5e9737efda16535e5b54bd627ef4881d11d31f – < 21ba85d9d508422ca9e6698463ff9357c928c22d
    • affected 7d5e9737efda16535e5b54bd627ef4881d11d31f – < 21a39b958b4bcf44f7674bfbbe1bbb8cad0d842d
    • affected 7d5e9737efda16535e5b54bd627ef4881d11d31f – < b6f56a44e4c1014b08859dcf04ed246500e310e5
  • Linux · Linux

    • affected 4.6
    • unaffected < 4.6
    • unaffected 5.4.300 – ≤ 5.4.*
    • unaffected 5.10.245 – ≤ 5.10.*
    • unaffected 5.15.194 – ≤ 5.15.*
    • unaffected 6.1.154 – ≤ 6.1.*
    • unaffected 6.6.108 – ≤ 6.6.*
    • unaffected 6.12.49 – ≤ 6.12.*
    • unaffected 6.16.9 – ≤ 6.16.*
    • unaffected 6.17 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-39937 badge
[![CVE-2025-39937](https://cveledger.app/badge/CVE-2025-39937.svg)](https://cveledger.app/cve/CVE-2025-39937)

Record last updated .