Answer in brief
CVE-2026-31598 records a High severity (CVSS 7.5) vulnerability in ocfs2: fix possible deadlock between unlink and dio_end_io_write. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=a86a72a4a4e0ec109a98e2737948864ed6794bf7 <297d8d7bb6a2bf133d3a3636edbdf94101cbd719 || >=a86a72a4a4e0ec109a98e2737948864ed6794bf7 <32630dee18c6bb2175c8a865a474749492eaf19c || >=a86a72a4a4e0ec109a98e2737948864ed6794bf7 <93f35419eb84d58820040642cb6e7528fe4aba7a || >=a86a72a4a4e0ec109a98e2737948864ed6794bf7 <4b80b5a838a32437f2cae0662578bac216a2c51a || >=a86a72a4a4e0ec109a98e2737948864ed6794bf7 <2b884d52273c60c298bd570163e8053657bbaff6 || >=a86a72a4a4e0ec109a98e2737948864ed6794bf7 <bc0fb5c7d54c78be43a536df0e20dee32adb27d3 || >=a86a72a4a4e0ec109a98e2737948864ed6794bf7 <f9fb1a7b635849322e1d7b7b6b26389778ec8e82 || >=a86a72a4a4e0ec109a98e2737948864ed6794bf7 <e049f7a9bd80b7319590789ea5e1c523d6339d91 || >=a86a72a4a4e0ec109a98e2737948864ed6794bf7 <b02da26a992db0c0e2559acbda0fc48d4a2fd337 | 297d8d7bb6a2bf133d3a3636edbdf94101cbd719, 32630dee18c6bb2175c8a865a474749492eaf19c, 93f35419eb84d58820040642cb6e7528fe4aba7a, 4b80b5a838a32437f2cae0662578bac216a2c51a, 2b884d52273c60c298bd570163e8053657bbaff6, bc0fb5c7d54c78be43a536df0e20dee32adb27d3, f9fb1a7b635849322e1d7b7b6b26389778ec8e82, e049f7a9bd80b7319590789ea5e1c523d6339d91, b02da26a992db0c0e2559acbda0fc48d4a2fd337 |
| Linux/Linuxgeneric | 4.6 | Not reported |
Published upstream
Apr 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 16, 2026
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.
Quoted source text, attributed separately from HOL analysis.