Vulnerability · CVE-2025-38243
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(),
Published Jul 9, 2025 · catalog updated May 11, 2026 · Linux Linux
Check this week
CVE-2025-38243 is not in CISA KEV. FIRST estimates a 16.00% chance of exploitation in the next 30 days. Check whether you run Linux Linux.
Gaps on this record
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- None0.0
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 16.00%
- Remediation
- Version ranges on file
- Affected products
- vendor Linux Linux b4c50cbb01a1b6901d2b94469636dd80fa93de81 <ba8386d662cc51cc5382688bbf7a152b0b0b27cf
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.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- vendor Linux Linux b4c50cbb01a1b6901d2b94469636dd80fa93de81 <ba8386d662cc51cc5382688bbf7a152b0b0b27cfb4c50cbb01a1b6901d2b94469636dd80fa93de81 <ba8386d662cc51cc5382688bbf7a152b0b0b27cf
How to fix CVE-2025-38243
Recommended remediation
Affected version ranges suggest a fixed boundary. Verify against the vendor advisory for your release.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
CVE-2025-38243 is not in CISA KEV. FIRST estimates a 16.00% chance of exploitation in the next 30 days. Check whether you run Linux Linux.
Which versions are affected?
Compare what you have installed with Linux Linux b4c50cbb01a1b6901d2b94469636dd80fa93de81 <ba8386d662cc51cc5382688bbf7a152b0b0b27cf b4c50cbb01a1b6901d2b94469636dd80fa93de81 <ba8386d662cc51cc5382688bbf7a152b0b0b27cf. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS 16.00%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Jul 9, 2025 · EUVD
Detected
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 tr
May 11, 2026 · EUVD
Updated
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 tr
Sources
- EUVDVulnerability recordEUVD-2025-20818
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
euvd.enisa.europa.eu
References
Freshness
Last verified in this catalog May 11, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.