CVE-2025-38726: Linux kernel · NULL Pointer Dereference
Source GCVE Database
Not known to be exploited · CVSS 5.5 Medium.
Data as of 19 Nov 2026, 02:26 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 for this vulnerability has been implemented in the Linux kernel. Users should apply the official kernel updates that include this patch to resolve the issue. Since this is a kernel-level vulnerability, updating to the fixed kernel version is the recommended mitigation.
Description
A vulnerability in the Linux kernel's ftgmac100 network driver could lead to a NULL pointer dereference in the ftgmac100_phy_disconnect function. This occurs because after calling phy_disconnect(), the netdev->phydev pointer is reset to NULL, but fixed_phy_unregister() is then called with this NULL pointer. The issue was fixed by caching the phy_device pointer before the call to avoid passing a NULL pointer.
References
- nvd.nist.gov/vuln/detail/CVE-2025-38726 (opens in a new tab)
- git.kernel.org/stable/c/44bcd397ad9cd1a6b25fabb7f5edbee4fb0cfc2e (opens in a new tab)
- git.kernel.org/stable/c/9ad90dd34b4e8e5be1e45a4559f4de0f14e53af2 (opens in a new tab)
- git.kernel.org/stable/c/ae59ec969c07c73f0610f8bd7e648f01e798d222 (opens in a new tab)
- git.kernel.org/stable/c/e88fbc30dda1cb7438515303704ceddb3ade4ecd (opens in a new tab)