Skip to main content
VulnerabilityPublished Updated

CVE-2026-31598: Linux kernel · ocfs2: fix possible deadlock between unlink and dio_end_io_write

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High · fixed in f9fb1a7b635849322e1d7b7b6b26389778ec8e82 : patch Linux kernel soon.

Data as of 26 Oct 2026, 14:18 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers can reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-10-16.

Patch
Available – fixed in f9fb1a7b635849322e1d7b7b6b26389778ec8e82, e049f7a9bd80b7319590789ea5e1c523d6339d91, bc0fb5c7d54c78be43a536df0e20dee32adb27d3 +6
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ a86a72a4a4e0ec109a98e2737948864ed6794bf7, < f9fb1a7b635849322e1d7b7b6b26389778ec8e82
Fixed in
  • f9fb1a7b635849322e1d7b7b6b26389778ec8e82
LinuxLinuxAffected
  • ≥ a86a72a4a4e0ec109a98e2737948864ed6794bf7, < e049f7a9bd80b7319590789ea5e1c523d6339d91
Fixed in
  • e049f7a9bd80b7319590789ea5e1c523d6339d91
LinuxLinuxAffected
  • ≥ a86a72a4a4e0ec109a98e2737948864ed6794bf7, < bc0fb5c7d54c78be43a536df0e20dee32adb27d3
Fixed in
  • bc0fb5c7d54c78be43a536df0e20dee32adb27d3
LinuxLinuxAffected
  • ≥ a86a72a4a4e0ec109a98e2737948864ed6794bf7, < b02da26a992db0c0e2559acbda0fc48d4a2fd337
Fixed in
  • b02da26a992db0c0e2559acbda0fc48d4a2fd337
LinuxLinuxAffected
  • ≥ a86a72a4a4e0ec109a98e2737948864ed6794bf7, < 32630dee18c6bb2175c8a865a474749492eaf19c
Fixed in
  • 32630dee18c6bb2175c8a865a474749492eaf19c
LinuxLinuxAffected
  • ≥ a86a72a4a4e0ec109a98e2737948864ed6794bf7, < 297d8d7bb6a2bf133d3a3636edbdf94101cbd719
Fixed in
  • 297d8d7bb6a2bf133d3a3636edbdf94101cbd719

AI-suggested

A fix is available and has been applied in multiple Linux kernel commits. Users and administrators should update affected Linux kernel versions to incorporate these fixes. Since this is a kernel-level deadlock fix, applying the official patches or upgrading to a fixed kernel version is the recommended mitigation.

Description

CVE-2026-31598 is a high-severity vulnerability in the Linux kernel's ocfs2 filesystem that could cause a deadlock due to inconsistent lock ordering between unlink and dio_end_io_write operations. The issue arises because ocfs2_unlink acquires locks in one order, while ocfs2_dio_end_io_write acquires them in the reverse order, creating an ABBA lock ordering violation. This deadlock can impact system availability. The vulnerability has been fixed by moving ocfs2_del_inode_from_orphan out of the ip_alloc_sem lock to prevent the deadlock.

References

Community reviews

Loading reviews…