Answer in brief
CVE-2026-80879 records a Unknown severity vulnerability in ocfs2: fix circular locking dependency in ocfs2_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.
A CVSS score is not reported in the current record. 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 | 7.1 | Not reported |
| Linux/Linuxgeneric | >=97c03c0e9f73a5049794b3c69ee60fb5e8b0ebd8 <f0ae0a6ca87dc2d4a789f71cdedb808ba6c16990 || >=1e99bb19994246514d63e656492904176f9d5edd <137e8b4823a9a11928428d4ec0a0cacb2f50a769 || >=91e05ac2336d00d5b99fc774be4bd50039084796 <4273548e418bd935430d35e9d052870f323441f3 || >=886f97fa59d0bbfa9859fb1a66dd9e014b522d89 <49b34bd3ad69611af03590a23abf2cda9ac1073d || >=ea5bb1d20da756e4f41a48dad42b2e7d6e73f71e <ff187c502b39389b0d732cb7050a3db8e5ebfcd6 || >=3c636a3edca9c3f180b3079f94fe7e115730d9c6 <ae1f3460833d3e427420ab260278ec0e45d68c86 || >=d647c5b2fbf81560818dacade360abc8c00a9665 <f3dd1e534e9de64669415f8239e0094afecfed78 || >=d647c5b2fbf81560818dacade360abc8c00a9665 <ff6f26c58421614b02694ac9d219ac61d924bc68 || 069c3fb310e9336cf48cfdf8748a32c29fd0193d || >=5.10.258 <5.10.261 || >=5.15.209 <5.15.212 || >=6.1.175 <6.1.178 || >=6.6.140 <6.6.145 || >=6.12.86 <6.12.97 || >=6.18.27 <6.18.40 || >=7.0.4 <7.1 | f0ae0a6ca87dc2d4a789f71cdedb808ba6c16990, 137e8b4823a9a11928428d4ec0a0cacb2f50a769, 4273548e418bd935430d35e9d052870f323441f3, 49b34bd3ad69611af03590a23abf2cda9ac1073d, ff187c502b39389b0d732cb7050a3db8e5ebfcd6, ae1f3460833d3e427420ab260278ec0e45d68c86, f3dd1e534e9de64669415f8239e0094afecfed78, ff6f26c58421614b02694ac9d219ac61d924bc68, 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.97, 6.18.40, 7.1 |
Published upstream
Sep 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 4, 2026
In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix circular locking dependency in ocfs2_dio_end_io_write A circular locking dependency involves INODE_ALLOC_SYSTEM_INODE, EXTENT_ALLOC_SYSTEM_INODE, and ORPHAN_DIR_SYSTEM_INODE. 1. ocfs2_mknod() acquires INODE_ALLOC then EXTENT_ALLOC. 2. ocfs2_dio_end_io_write() acquires EXTENT_ALLOC for unwritten extents, then ORPHAN_DIR via ocfs2_del_inode_from_orphan() while still holding EXTENT_ALLOC. 3. ocfs2_wipe_inode() acquires ORPHAN_DIR then INODE_ALLOC via ocfs2_remove_inode. Break the cycle in ocfs2_dio_end_io_write() by freeing the allocation contexts (releasing EXTENT_ALLOC) before acquiring ORPHAN_DIR. WARNING: possible circular locking dependency detected ------------------------------------------------------ is trying to acquire lock: ffff8881e78b33a0 (&ocfs2_sysfile_lock_key[INODE_ALLOC_SYSTEM_INODE]){+.+.}-{4:4}, at: ocfs2_evict_inode+0x1539/0x43b0 fs/ocfs2/inode.c:1299 but task is already holding lock: ffff8881e78b4fa0 (&ocfs2_sysfile_lock_key[ORPHAN_DIR_SYSTEM_INODE]){+.+.}-{4:4}, at: ocfs2_evict_inode+0xe97/0x43b0 fs/ocfs2/inode.c:1299 the existing dependency chain (in reverse order) is: -> #2 (&ocfs2_sysfile_lock_key[ORPHAN_DIR_SYSTEM_INODE]){+.+.}-{4:4}: inode_lock include/linux/fs.h:1029 [inline] ocfs2_del_inode_from_orphan+0x12e/0x7a0 fs/ocfs2/namei.c:2728 ocfs2_dio_end_io+0xf9c/0x1370 fs/ocfs2/aops.c:2418 dio_complete+0x25b/0x790 fs/direct-io.c:281 -> #1 (&ocfs2_sysfile_lock_key[EXTENT_ALLOC_SYSTEM_INODE]){+.+.}-{4:4}: inode_lock include/linux/fs.h:1029 [inline] ocfs2_reserve_suballoc_bits+0x16d/0x4840 fs/ocfs2/suballoc.c:882 ocfs2_reserve_new_metadata_blocks+0x415/0x9a0 fs/ocfs2/suballoc.c:1078 ocfs2_mknod+0x10f3/0x2260 fs/ocfs2/namei.c:351 -> #0 (&ocfs2_sysfile_lock_key[INODE_ALLOC_SYSTEM_INODE]){+.+.}-{4:4}: __lock_acquire+0x15a5/0x2cf0 kernel/locking/lockdep.c:5237 lock_acquire+0x106/0x350 kernel/locking/lockdep.c:5868 down_write+0x96/0x200 kernel/locking/rwsem.c:1625 inode_lock include/linux/fs.h:1029 [inline] ocfs2_remove_inode fs/ocfs2/inode.c:733 [inline] ocfs2_wipe_inode fs/ocfs2/inode.c:896 [inline] ocfs2_delete_inode fs/ocfs2/inode.c:1157 [inline] ocfs2_evict_inode+0x1539/0x43b0 fs/ocfs2/inode.c:1299 Chain exists of: &ocfs2_sysfile_lock_key[INODE_ALLOC_SYSTEM_INODE] --> &ocfs2_sysfile_lock_key[EXTENT_ALLOC_SYSTEM_INODE] --> &ocfs2_sysfile_lock_key[ORPHAN_DIR_SYSTEM_INODE] Possible unsafe locking scenario: CPU0 CPU1 ---- ---- lock(&ocfs2_sysfile_lock_key[ORPHAN_DIR_SYSTEM_INODE]); lock(&ocfs2_sysfile_lock_key[EXTENT_ALLOC_SYSTEM_INODE]); lock(&ocfs2_sysfile_lock_key[ORPHAN_DIR_SYSTEM_INODE]); lock(&ocfs2_sysfile_lock_key[INODE_ALLOC_SYSTEM_INODE]); *** DEADLOCK ***
Quoted source text, attributed separately from HOL analysis.