CVE-2026-80879ocfs2: fix circular locking dependency in ocfs2_dio_end_io_write
- —Not scoredno CVSS score yet
- 0.17%Exploitation in 30 daysEPSS · top 94% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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 ***
Timeline
ID reserved
By Linux
- 9 days later
· 9 days later
Published
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.17% · top 94% of all CVEs (14 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 97c03c0e9f73a5049794b3c69ee60fb5e8b0ebd8 – < f0ae0a6ca87dc2d4a789f71cdedb808ba6c16990
- affected 1e99bb19994246514d63e656492904176f9d5edd – < 137e8b4823a9a11928428d4ec0a0cacb2f50a769
- affected 91e05ac2336d00d5b99fc774be4bd50039084796 – < 4273548e418bd935430d35e9d052870f323441f3
- affected 886f97fa59d0bbfa9859fb1a66dd9e014b522d89 – < 49b34bd3ad69611af03590a23abf2cda9ac1073d
- affected ea5bb1d20da756e4f41a48dad42b2e7d6e73f71e – < ff187c502b39389b0d732cb7050a3db8e5ebfcd6
- affected 3c636a3edca9c3f180b3079f94fe7e115730d9c6 – < ae1f3460833d3e427420ab260278ec0e45d68c86
- affected d647c5b2fbf81560818dacade360abc8c00a9665 – < f3dd1e534e9de64669415f8239e0094afecfed78
- affected d647c5b2fbf81560818dacade360abc8c00a9665 – < ff6f26c58421614b02694ac9d219ac61d924bc68
- affected 069c3fb310e9336cf48cfdf8748a32c29fd0193d
- affected 5.10.258 – < 5.10.261
- affected 5.15.209 – < 5.15.212
- affected 6.1.175 – < 6.1.178
- affected 6.6.140 – < 6.6.145
- affected 6.12.86 – < 6.12.97
- affected 6.18.27 – < 6.18.40
- affected 7.0.4 – < 7.1
- affected 7.1
- unaffected < 7.1
- unaffected 5.10.261 – ≤ 5.10.*
- unaffected 5.15.212 – ≤ 5.15.*
- unaffected 6.1.178 – ≤ 6.1.*
- unaffected 6.6.145 – ≤ 6.6.*
- unaffected 6.12.97 – ≤ 6.12.*
- unaffected 6.18.40 – ≤ 6.18.*
- unaffected 7.1.5 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References8
- https://git.kernel.org/stable/c/f0ae0a6ca87dc2d4a789f71cdedb808ba6c16990 (opens in a new tab)
- https://git.kernel.org/stable/c/137e8b4823a9a11928428d4ec0a0cacb2f50a769 (opens in a new tab)
- https://git.kernel.org/stable/c/4273548e418bd935430d35e9d052870f323441f3 (opens in a new tab)
- https://git.kernel.org/stable/c/49b34bd3ad69611af03590a23abf2cda9ac1073d (opens in a new tab)
- https://git.kernel.org/stable/c/ff187c502b39389b0d732cb7050a3db8e5ebfcd6 (opens in a new tab)
- https://git.kernel.org/stable/c/ae1f3460833d3e427420ab260278ec0e45d68c86 (opens in a new tab)
- https://git.kernel.org/stable/c/f3dd1e534e9de64669415f8239e0094afecfed78 (opens in a new tab)
- https://git.kernel.org/stable/c/ff6f26c58421614b02694ac9d219ac61d924bc68 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-71509 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-80879)Record last updated .