CVE-2025-39707: Linux kernel · drm/amdgpu: check if hubbub is NULL in debugfs/amdgpu_dm_capabilities
Source GCVE Database
Not known to be exploited · CVSS 5.5 Medium.
Data as of 19 Nov 2026, 02:21 UTC
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 5 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
AI-suggested
A fix has been implemented in the Linux kernel to check if the HUBBUB pointer is NULL before accessing it, preventing null dereference. Users should update to the fixed kernel version once available. No other mitigation is indicated.
Description
A null pointer dereference vulnerability was identified and resolved in the Linux kernel's AMDGPU driver. The issue occurs because the HUBBUB structure is not initialized on DCE hardware, leading to a potential null dereference when accessing the amdgpu_dm_capabilities file in debugfs. This flaw could cause a denial of service due to kernel crash.
References
- nvd.nist.gov/vuln/detail/CVE-2025-39707 (opens in a new tab)
- git.kernel.org/stable/c/83cfdc2b018cd9c0f927b781d4e07c0d4a911fac (opens in a new tab)
- git.kernel.org/stable/c/98e92fceb9507901e3e8b550e93b843306abd354 (opens in a new tab)
- git.kernel.org/stable/c/b4a69f7f29c8a459ad6b4d8a8b72450f1d9fd288 (opens in a new tab)