CVE-2025-38243: Linux kernel · NULL Pointer Dereference
Source GCVE Database
Not known to be exploited · CVSS 5.5 Medium.
Data as of 13 Nov 2026, 18:29 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 9 Jul 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 13 Nov 2026.
Description
In the Linux kernel, the following vulnerability has been resolved: btrfs: fix invalid inode pointer dereferences during log replay In a few places where we call read_one_inode(), if we get a NULL pointer we end up jumping into an error path, or fallthrough in case of __add_inode_ref(), where we then do something like this: iput(&inode->vfs_inode); which results in an invalid inode pointer that triggers an invalid memory access, resulting in a crash. Fix this by making sure we don't do such dereferences.
References
- nvd.nist.gov/vuln/detail/CVE-2025-38243 (opens in a new tab)
- git.kernel.org/stable/c/2dcf838cf5c2f0f4501edaa1680fcad03618d760 (opens in a new tab)
- git.kernel.org/stable/c/401d098f92ea69d8a75f8b845daf343e511681ba (opens in a new tab)
- git.kernel.org/stable/c/ba8386d662cc51cc5382688bbf7a152b0b0b27cf (opens in a new tab)