{"api_version":"1","generated_at":"2026-09-12T11:51:21+00:00","cve":"CVE-2026-89491","urls":{"html":"https://cve.report/CVE-2026-89491","api":"https://cve.report/api/cve/CVE-2026-89491.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-89491","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-89491"},"summary":{"title":"ocfs2: cluster: don't sleep while holding o2hb_live_lock in o2hb_region_pin()","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nocfs2: cluster: don't sleep while holding o2hb_live_lock in o2hb_region_pin()\n\nPatch series \"ocfs2: cluster: o2hb_region_pin() fixes\", v2.\n\nThis series fixes three related issues in o2hb_region_pin(), all are from\nthe original implementation in commit: 58a3158a5d17 (\"ocfs2/cluster:\nPin/unpin o2hb regions\"):\n\n1) It is called with o2hb_live_lock (a spinlock) held, but the\n   underlying configfs_depend_item() sleeps (takes inode rwsem and\n   pins the filesystem).  This triggers BUG under\n   CONFIG_DEBUG_ATOMIC_SLEEP.\n\n2) When called from the configfs drop_item callback, it creates a\n   lock order inversion: parent inode_lock -> configfs root\n   inode_lock, which can deadlock against subsystem unregistration\n   paths taking root -> parent.\n\n3) If pinning fails partway through o2hb_region_inc_user(), the\n   o2hb_dependent_users counter is leaked and partially-pinned\n   regions are never released, leaving heartbeat regions\n   unprotected on subsequent mounts.\n\nPatch 1 reworks o2hb_region_pin() to drop o2hb_live_lock across each\nsleeping configfs_depend_item() call, using a config_item reference to\nkeep the region alive while unlocked.\n\nPatch 2 adds a from_callback parameter to select\nconfigfs_depend_item_unlocked() when called from configfs context,\navoiding the inode_lock nesting.\n\nPatch 3 fixes the error path in o2hb_region_inc_user() to unpin and\ndecrement the counter on failure.\n\n\nThis patch (of 3):\n\no2hb_region_pin() is always called with the o2hb_live_lock spinlock held\n(from o2hb_region_inc_user() and o2hb_heartbeat_group_drop_item()), but it\ncalls o2nm_depend_item() -> configfs_depend_item(), which sleeps: it pins\nthe configfs filesystem and takes the configfs root inode rwsem.  Under\nCONFIG_DEBUG_ATOMIC_SLEEP this triggers:\n\n  BUG: sleeping function called from invalid context at kernel/locking/rwsem.c\n  in_atomic(): 1, ... name: mount.ocfs2\n    down_write\n    configfs_depend_item\n    o2hb_region_pin\n    o2hb_region_inc_user\n    o2hb_register_callback\n    dlm_register_domain_handlers\n    ...\n    ocfs2_dlm_init\n    ocfs2_mount_volume\n    ocfs2_fill_super\n\nRework o2hb_region_pin() to pin one region at a time with the lock dropped\nacross the sleeping call: under o2hb_live_lock find the next eligible\nregion and take a config_item reference to keep it alive, drop the lock,\ncall o2nm_depend_item(), then retake the lock and record the pin.  The\nconfig_item_put() is done with the lock released as well, since\no2hb_region_release() also acquires o2hb_live_lock and can sleep.  The\nregion list may change while unlocked, so the scan restarts from the top\nafter each pin.  Local heartbeat still pins only the matching region;\nglobal heartbeat pins all eligible regions.\n\nThe unpin path is unaffected: configfs_undepend_item() only takes a\nspinlock and does not sleep.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-11 20:19:30","updated_at":"2026-09-11 20:19:30"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/49002acc520c61002ad195894ac391c94317d3ba","name":"https://git.kernel.org/stable/c/49002acc520c61002ad195894ac391c94317d3ba","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/470212a5eefabcc16b8e2f7fe2844b8737fe571c","name":"https://git.kernel.org/stable/c/470212a5eefabcc16b8e2f7fe2844b8737fe571c","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/ce035f208d68b812d83e5482980f2b1c88a9cd94","name":"https://git.kernel.org/stable/c/ce035f208d68b812d83e5482980f2b1c88a9cd94","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/af09df89db9a68a1d76df0f75667998135bc8d65","name":"https://git.kernel.org/stable/c/af09df89db9a68a1d76df0f75667998135bc8d65","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-89491","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-89491","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 58a3158a5d17ddf4894db9e8ccaf92093ff8e42e 49002acc520c61002ad195894ac391c94317d3ba git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 58a3158a5d17ddf4894db9e8ccaf92093ff8e42e ce035f208d68b812d83e5482980f2b1c88a9cd94 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 58a3158a5d17ddf4894db9e8ccaf92093ff8e42e 470212a5eefabcc16b8e2f7fe2844b8737fe571c git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 58a3158a5d17ddf4894db9e8ccaf92093ff8e42e af09df89db9a68a1d76df0f75667998135bc8d65 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 2.6.38","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 2.6.38 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.109 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.50 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.4 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3-rc1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["fs/ocfs2/cluster/heartbeat.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"49002acc520c61002ad195894ac391c94317d3ba","status":"affected","version":"58a3158a5d17ddf4894db9e8ccaf92093ff8e42e","versionType":"git"},{"lessThan":"ce035f208d68b812d83e5482980f2b1c88a9cd94","status":"affected","version":"58a3158a5d17ddf4894db9e8ccaf92093ff8e42e","versionType":"git"},{"lessThan":"470212a5eefabcc16b8e2f7fe2844b8737fe571c","status":"affected","version":"58a3158a5d17ddf4894db9e8ccaf92093ff8e42e","versionType":"git"},{"lessThan":"af09df89db9a68a1d76df0f75667998135bc8d65","status":"affected","version":"58a3158a5d17ddf4894db9e8ccaf92093ff8e42e","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["fs/ocfs2/cluster/heartbeat.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"2.6.38"},{"lessThan":"2.6.38","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.109","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.50","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.4","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3-rc1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.109","versionStartIncluding":"2.6.38","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.50","versionStartIncluding":"2.6.38","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.4","versionStartIncluding":"2.6.38","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3-rc1","versionStartIncluding":"2.6.38","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nocfs2: cluster: don't sleep while holding o2hb_live_lock in o2hb_region_pin()\n\nPatch series \"ocfs2: cluster: o2hb_region_pin() fixes\", v2.\n\nThis series fixes three related issues in o2hb_region_pin(), all are from\nthe original implementation in commit: 58a3158a5d17 (\"ocfs2/cluster:\nPin/unpin o2hb regions\"):\n\n1) It is called with o2hb_live_lock (a spinlock) held, but the\n   underlying configfs_depend_item() sleeps (takes inode rwsem and\n   pins the filesystem).  This triggers BUG under\n   CONFIG_DEBUG_ATOMIC_SLEEP.\n\n2) When called from the configfs drop_item callback, it creates a\n   lock order inversion: parent inode_lock -> configfs root\n   inode_lock, which can deadlock against subsystem unregistration\n   paths taking root -> parent.\n\n3) If pinning fails partway through o2hb_region_inc_user(), the\n   o2hb_dependent_users counter is leaked and partially-pinned\n   regions are never released, leaving heartbeat regions\n   unprotected on subsequent mounts.\n\nPatch 1 reworks o2hb_region_pin() to drop o2hb_live_lock across each\nsleeping configfs_depend_item() call, using a config_item reference to\nkeep the region alive while unlocked.\n\nPatch 2 adds a from_callback parameter to select\nconfigfs_depend_item_unlocked() when called from configfs context,\navoiding the inode_lock nesting.\n\nPatch 3 fixes the error path in o2hb_region_inc_user() to unpin and\ndecrement the counter on failure.\n\n\nThis patch (of 3):\n\no2hb_region_pin() is always called with the o2hb_live_lock spinlock held\n(from o2hb_region_inc_user() and o2hb_heartbeat_group_drop_item()), but it\ncalls o2nm_depend_item() -> configfs_depend_item(), which sleeps: it pins\nthe configfs filesystem and takes the configfs root inode rwsem.  Under\nCONFIG_DEBUG_ATOMIC_SLEEP this triggers:\n\n  BUG: sleeping function called from invalid context at kernel/locking/rwsem.c\n  in_atomic(): 1, ... name: mount.ocfs2\n    down_write\n    configfs_depend_item\n    o2hb_region_pin\n    o2hb_region_inc_user\n    o2hb_register_callback\n    dlm_register_domain_handlers\n    ...\n    ocfs2_dlm_init\n    ocfs2_mount_volume\n    ocfs2_fill_super\n\nRework o2hb_region_pin() to pin one region at a time with the lock dropped\nacross the sleeping call: under o2hb_live_lock find the next eligible\nregion and take a config_item reference to keep it alive, drop the lock,\ncall o2nm_depend_item(), then retake the lock and record the pin.  The\nconfig_item_put() is done with the lock released as well, since\no2hb_region_release() also acquires o2hb_live_lock and can sleep.  The\nregion list may change while unlocked, so the scan restarts from the top\nafter each pin.  Local heartbeat still pins only the matching region;\nglobal heartbeat pins all eligible regions.\n\nThe unpin path is unaffected: configfs_undepend_item() only takes a\nspinlock and does not sleep."}],"providerMetadata":{"dateUpdated":"2026-09-11T19:43:43.466Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/49002acc520c61002ad195894ac391c94317d3ba"},{"url":"https://git.kernel.org/stable/c/ce035f208d68b812d83e5482980f2b1c88a9cd94"},{"url":"https://git.kernel.org/stable/c/470212a5eefabcc16b8e2f7fe2844b8737fe571c"},{"url":"https://git.kernel.org/stable/c/af09df89db9a68a1d76df0f75667998135bc8d65"}],"title":"ocfs2: cluster: don't sleep while holding o2hb_live_lock in o2hb_region_pin()","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-89491","datePublished":"2026-09-11T19:43:43.466Z","dateReserved":"2026-09-11T19:38:34.713Z","dateUpdated":"2026-09-11T19:43:43.466Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-11 20:19:30","lastModifiedDate":"2026-09-11 20:19:30","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"89491","Ordinal":"1","Title":"ocfs2: cluster: don't sleep while holding o2hb_live_lock in o2hb","CVE":"CVE-2026-89491","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"89491","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nocfs2: cluster: don't sleep while holding o2hb_live_lock in o2hb_region_pin()\n\nPatch series \"ocfs2: cluster: o2hb_region_pin() fixes\", v2.\n\nThis series fixes three related issues in o2hb_region_pin(), all are from\nthe original implementation in commit: 58a3158a5d17 (\"ocfs2/cluster:\nPin/unpin o2hb regions\"):\n\n1) It is called with o2hb_live_lock (a spinlock) held, but the\n   underlying configfs_depend_item() sleeps (takes inode rwsem and\n   pins the filesystem).  This triggers BUG under\n   CONFIG_DEBUG_ATOMIC_SLEEP.\n\n2) When called from the configfs drop_item callback, it creates a\n   lock order inversion: parent inode_lock -> configfs root\n   inode_lock, which can deadlock against subsystem unregistration\n   paths taking root -> parent.\n\n3) If pinning fails partway through o2hb_region_inc_user(), the\n   o2hb_dependent_users counter is leaked and partially-pinned\n   regions are never released, leaving heartbeat regions\n   unprotected on subsequent mounts.\n\nPatch 1 reworks o2hb_region_pin() to drop o2hb_live_lock across each\nsleeping configfs_depend_item() call, using a config_item reference to\nkeep the region alive while unlocked.\n\nPatch 2 adds a from_callback parameter to select\nconfigfs_depend_item_unlocked() when called from configfs context,\navoiding the inode_lock nesting.\n\nPatch 3 fixes the error path in o2hb_region_inc_user() to unpin and\ndecrement the counter on failure.\n\n\nThis patch (of 3):\n\no2hb_region_pin() is always called with the o2hb_live_lock spinlock held\n(from o2hb_region_inc_user() and o2hb_heartbeat_group_drop_item()), but it\ncalls o2nm_depend_item() -> configfs_depend_item(), which sleeps: it pins\nthe configfs filesystem and takes the configfs root inode rwsem.  Under\nCONFIG_DEBUG_ATOMIC_SLEEP this triggers:\n\n  BUG: sleeping function called from invalid context at kernel/locking/rwsem.c\n  in_atomic(): 1, ... name: mount.ocfs2\n    down_write\n    configfs_depend_item\n    o2hb_region_pin\n    o2hb_region_inc_user\n    o2hb_register_callback\n    dlm_register_domain_handlers\n    ...\n    ocfs2_dlm_init\n    ocfs2_mount_volume\n    ocfs2_fill_super\n\nRework o2hb_region_pin() to pin one region at a time with the lock dropped\nacross the sleeping call: under o2hb_live_lock find the next eligible\nregion and take a config_item reference to keep it alive, drop the lock,\ncall o2nm_depend_item(), then retake the lock and record the pin.  The\nconfig_item_put() is done with the lock released as well, since\no2hb_region_release() also acquires o2hb_live_lock and can sleep.  The\nregion list may change while unlocked, so the scan restarts from the top\nafter each pin.  Local heartbeat still pins only the matching region;\nglobal heartbeat pins all eligible regions.\n\nThe unpin path is unaffected: configfs_undepend_item() only takes a\nspinlock and does not sleep.","Type":"Description","Title":"ocfs2: cluster: don't sleep while holding o2hb_live_lock in o2hb"}]}}}