⚠ Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● High · CVSS 7.8

How to Fix CVE-2026-31597: ocfs2: fix use-after-free in Linux

By Sai Kiran Pandrala

Other vulnerabilities in the same area that are worth patching alongside this one:

Last verified: 2026-05-25

CVE-2026-31597 is a ocfs2: fix use-after-free in Linux Linux. Fix it by upgrading to 6.6.136, 6.12.83, 6.18.24, 6.19.14, 7.0.1, 7.1-rc1.

⚡ At a glance
SeverityCVSS 7.8 - High
Actively exploited?Not currently in the CISA KEV catalog
AffectedLinux 614a9e849ca6ea24843795251cb30af525d5336b up to (excluding) 6f072daefcab1d84ce37c073645615f63be91006; Linux 614a9e849ca6ea24843795251cb30af525d5336b up to (excluding) 4cf2768a0291a0cdd0dae801ea0eafa3878a349d; Linux 614a9e849ca6ea24843795251cb30af525d5336b up to (excluding) d45ff441b416d4aa1af72b1db23d959601c04da2; Linux 614a9e849ca6ea24843795251cb30af525d5336b up to (excluding) 76a602fdbb78dd05b2da06f74a988cebc97e82d0; Linux 614a9e849ca6ea24843795251cb30af525d5336b up to (excluding) 925bf22c1b823e231b1baea761fe8a1512e442f2; Linux 614a9e849ca6ea24843795251cb30af525d5336b up to (excluding) 7de554cabf160e331e4442e2a9ad874ca9875921
Fixed in6.6.136, 6.12.83, 6.18.24, 6.19.14, 7.0.1, 7.1-rc1
Type (CWE)Not verified

What is CVE-2026-31597?

CVE-2026-31597 is a ocfs2: fix use-after-free flaw in Linux Linux. It carries a CVSS base score of 7.8 (high). It is not currently listed in the CISA Known Exploited Vulnerabilities catalog.

From the source record: 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.

Why it matters in practice: The blast radius depends on how the affected service is exposed. An internet-facing instance with no compensating controls is the highest-risk configuration.

Am I affected?

You are affected if your installation of Linux matches a version listed in the Affected row above.


# Debian/Ubuntu
dpkg -s linux | grep Version
# RHEL/Rocky
rpm -q linux

How to fix CVE-2026-31597

Apply the vendor patch. Target the build named in the Fixed in row above (6.6.136, 6.12.83, 6.18.24, 6.19.14, 7.0.1, 7.1-rc1). The runnable command set below covers the most common deployment patterns for Linux.

Ubuntu / Debian


sudo apt-get update
sudo apt-get install --only-upgrade linux
dpkg -s linux | grep Version

RHEL / CentOS / Rocky


sudo dnf upgrade linux -y
rpm -q linux

After applying the patch

  1. Restart the service or device so the patched binary loads.
  2. Confirm the running version matches the Fixed in row using the verification command below.
  3. Rotate credentials and API keys that the affected service could access if the asset was exposed during the disclosure window.

If you can't patch immediately

Until the patch lands, narrow the attack surface with these runnable controls.

Restrict network exposure

Block public access to the affected service at the perimeter. Allow only trusted source IPs.


# Linux iptables: only allow trusted admin subnet
sudo iptables -A INPUT -p tcp --dport 443 -s 10.10.10.0/24 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 443 -j DROP
sudo iptables-save | sudo tee /etc/iptables/rules.v4


# Windows firewall: only allow trusted admin subnet on management port
New-NetFirewallRule -DisplayName "Restrict-Mgmt-Allow" -Direction Inbound -Action Allow `
  -RemoteAddress 10.10.10.0/24 -Protocol TCP -LocalPort 443
New-NetFirewallRule -DisplayName "Restrict-Mgmt-Deny"  -Direction Inbound -Action Block `
  -Protocol TCP -LocalPort 443

Mitigations are temporary. Apply the vendor patch as soon as a maintenance window opens.

How to verify the fix worked

Confirm the patched build is the one actually running.


# Debian/Ubuntu
dpkg -s linux | grep Version
# RHEL/Rocky
rpm -q linux

Expected: a version at or above 6.6.136, 6.12.83, 6.18.24, 6.19.14, 7.0.1, 7.1-rc1.

Also worth doing: pull recent log windows for indicators of compromise listed in the vendor advisory, and re-run an authenticated vulnerability scan with up-to-date signatures.

Frequently asked questions

Is CVE-2026-31597 being exploited in the wild?

As of 2026-05-25, CVE-2026-31597 is not listed in the CISA Known Exploited Vulnerabilities catalog. Watch the catalog and patch on a normal cadence; KEV status can change as exploitation evidence emerges.

What is the CVSS score for CVE-2026-31597?

The CVSS base score is 7.8 (High).

What version fixes this?

Upgrade to 6.6.136, 6.12.83, 6.18.24, 6.19.14, 7.0.1, 7.1-rc1.

Will a WAF or IDS rule alone close this?

No. Network filters cut down opportunistic scans but they do not remove the flaw. The vendor patch is the only durable fix.

References

*Assembled from the official vendor advisory, the NVD record, and the CISA KEV listing on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*