CVE-2026-31597 json
ocfs2: fix use-after-free in ocfs2_fault() when VM_FAULT_RETRY
published 2026-04-24 6 mo ago modified 2026-08-05 3 mo ago also EUVD-2026-25490
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 2%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 5.10.258, 5.15.209, 6.1.175, 6.6.136, 6.12.83, 6.18.24, 6.19.14, 7.0.1, 7.1
- linux Debian 12 6.1.176-1
- linux Debian 13 6.12.85-1
- linux Debian 14 6.19.14-1
debian advisories DEBIAN-CVE-2026-31597
- linux Ubuntu 22.04 LTS 5.15.0-186.196
- linux Ubuntu 24.04 LTS 6.8.0-136.136
- linux Ubuntu 26.04 LTS 7.0.0-27.27
- linux-aws Ubuntu 22.04 LTS 5.15.0-1112.119
- linux-aws Ubuntu 24.04 LTS 6.8.0-1061.64
- linux-aws Ubuntu 26.04 LTS 7.0.0-1008.8
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1112.122
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1064.72
ubuntu advisories UBUNTU-CVE-2026-31597
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-source openSUSE Tumbleweed 7.0.3-1.1
opensuse advisories openSUSE-SU-2026:10703-1
- git.kernel.org/stable/c/36539c4d536f851a3b346a6ebb27b51bc3d77a94 commit
- git.kernel.org/stable/c/35c2c05261d6f6d84aaa1355afa201d507943e76 commit
- git.kernel.org/stable/c/3f5e74b5db9353b01ed50f4de84e75b755f8fbc2 commit
- git.kernel.org/stable/c/6f072daefcab1d84ce37c073645615f63be91006 commit
- git.kernel.org/stable/c/4cf2768a0291a0cdd0dae801ea0eafa3878a349d commit
- git.kernel.org/stable/c/d45ff441b416d4aa1af72b1db23d959601c04da2 commit
- git.kernel.org/stable/c/76a602fdbb78dd05b2da06f74a988cebc97e82d0 commit
- git.kernel.org/stable/c/925bf22c1b823e231b1baea761fe8a1512e442f2 commit
- git.kernel.org/stable/c/7de554cabf160e331e4442e2a9ad874ca9875921 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-31597 updated
kernel: ocfs2: fix use-after-free in ocfs2_fault() when VM_FAULT_RETRY
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.13% chance of exploitation in the next 30 days, higher than 2% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-416 Use After Free
- Technology feeds
References
- git.kernel.org /stable/c/36539c4d536f851a3b346a6ebb27b51bc3d77a94
- git.kernel.org /stable/c/35c2c05261d6f6d84aaa1355afa201d507943e76
- git.kernel.org /stable/c/3f5e74b5db9353b01ed50f4de84e75b755f8fbc2
-
git.kernel.org
/stable/c/6f072daefcab1d84ce37c073645615f63be91006
patch
-
git.kernel.org
/stable/c/4cf2768a0291a0cdd0dae801ea0eafa3878a349d
patch
-
git.kernel.org
/stable/c/d45ff441b416d4aa1af72b1db23d959601c04da2
patch
-
git.kernel.org
/stable/c/76a602fdbb78dd05b2da06f74a988cebc97e82d0
patch
-
git.kernel.org
/stable/c/925bf22c1b823e231b1baea761fe8a1512e442f2
patch
-
git.kernel.org
/stable/c/7de554cabf160e331e4442e2a9ad874ca9875921
patch
Sources
- CVE List CVE-2026-31597
- NVD CVE-2026-31597
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.