CVE-2026-31598ocfs2: fix possible deadlock between unlink and dio_end_io_write
Updated under an hour ago ()
Does this affect you?
It affects Linux and 1 other product. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix possible deadlock between unlink and dio_end_io_write ocfs2_unlink takes orphan dir inode_lock first and then ip_alloc_sem, while in ocfs2_dio_end_io_write, it acquires these locks in reverse order. This creates an ABBA lock ordering violation on lock classes ocfs2_sysfile_lock_key[ORPHAN_DIR_SYSTEM_INODE] and ocfs2_file_ip_alloc_sem_key. Lock Chain #0 (orphan dir inode_lock -> ip_alloc_sem): ocfs2_unlink ocfs2_prepare_orphan_dir ocfs2_lookup_lock_orphan_dir inode_lock(orphan_dir_inode) <- lock A __ocfs2_prepare_orphan_dir ocfs2_prepare_dir_for_insert ocfs2_extend_dir ocfs2_expand_inline_dir down_write(&oi->ip_alloc_sem) <- Lock B Lock Chain #1 (ip_alloc_sem -> orphan dir inode_lock): ocfs2_dio_end_io_write down_write(&oi->ip_alloc_sem) <- Lock B ocfs2_del_inode_from_orphan() inode_lock(orphan_dir_inode) <- Lock A Deadlock Scenario: CPU0 (unlink) CPU1 (dio_end_io_write) ------ ------ inode_lock(orphan_dir_inode) down_write(ip_alloc_sem) down_write(ip_alloc_sem) inode_lock(orphan_dir_inode) Since ip_alloc_sem is to protect allocation changes, which is unrelated with operations in ocfs2_del_inode_from_orphan. So move ocfs2_del_inode_from_orphan out of ip_alloc_sem to fix the deadlock.
- CVSS
- 7.5 HIGH (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Modified
- Record last updated
- Oct 16, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from a86a72a4a4e0ec109a98e2737948864ed6794bf7 before 297d8d7bb6a2bf133d3a3636edbdf94101cbd719; from a86a72a4a4e0ec109a98e2737948864ed6794bf7 before 32630dee18c6bb2175c8a865a474749492eaf19c; from a86a72a4a4e0ec109a98e2737948864ed6794bf7 before 93f35419eb84d58820040642cb6e7528fe4aba7a; from a86a72a4a4e0ec109a98e2737948864ed6794bf7 before 4b80b5a838a32437f2cae0662578bac216a2c51a; from a86a72a4a4e0ec109a98e2737948864ed6794bf7 before 2b884d52273c60c298bd570163e8053657bbaff6; from a86a72a4a4e0ec109a98e2737948864ed6794bf7 before bc0fb5c7d54c78be43a536df0e20dee32adb27d3; from a86a72a4a4e0ec109a98e2737948864ed6794bf7 before f9fb1a7b635849322e1d7b7b6b26389778ec8e82; from a86a72a4a4e0ec109a98e2737948864ed6794bf7 before e049f7a9bd80b7319590789ea5e1c523d6339d91; and 1 more ranges | CNA record |
linux linux_kernel linux:linux_kernel | from 4.6 before 6.6.136; from 6.7 before 6.12.83; from 6.13 before 6.18.24; from 6.19 before 6.19.14; from 7.0 before 7.0.1 | NVD |
References
- https://git.kernel.org/stable/c/297d8d7bb6a2bf133d3a3636edbdf94101cbd719
- https://git.kernel.org/stable/c/32630dee18c6bb2175c8a865a474749492eaf19c
- https://git.kernel.org/stable/c/93f35419eb84d58820040642cb6e7528fe4aba7a
- https://git.kernel.org/stable/c/4b80b5a838a32437f2cae0662578bac216a2c51apatch
- https://git.kernel.org/stable/c/2b884d52273c60c298bd570163e8053657bbaff6patch
- https://git.kernel.org/stable/c/bc0fb5c7d54c78be43a536df0e20dee32adb27d3patch
- https://git.kernel.org/stable/c/f9fb1a7b635849322e1d7b7b6b26389778ec8e82patch
- https://git.kernel.org/stable/c/e049f7a9bd80b7319590789ea5e1c523d6339d91patch
- https://git.kernel.org/stable/c/b02da26a992db0c0e2559acbda0fc48d4a2fd337patch
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.