FKIE_CVE-2026-89491
Vulnerability from fkie_nvd - Published: 2026-09-11 20:19 - Updated: 2026-10-19 09:17| Vendor | Product | Version |
|---|
{
"affected": [
{
"affectedData": [
{
"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": "4d64f8da82fb9e8dbd5aa9b64c9bb6ac0decea03",
"status": "affected",
"version": "58a3158a5d17ddf4894db9e8ccaf92093ff8e42e",
"versionType": "git"
},
{
"lessThan": "3b790774280a610f8bdbd5d4260a07345bcf8e04",
"status": "affected",
"version": "58a3158a5d17ddf4894db9e8ccaf92093ff8e42e",
"versionType": "git"
},
{
"lessThan": "0cbc2f20a6ea7b4a59efa9171b7c694cdd196507",
"status": "affected",
"version": "58a3158a5d17ddf4894db9e8ccaf92093ff8e42e",
"versionType": "git"
},
{
"lessThan": "c9be4de77f97f383b750698e1517fd296041f4bb",
"status": "affected",
"version": "58a3158a5d17ddf4894db9e8ccaf92093ff8e42e",
"versionType": "git"
},
{
"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": "5.10.*",
"status": "unaffected",
"version": "5.10.270",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.15.*",
"status": "unaffected",
"version": "5.15.221",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.1.*",
"status": "unaffected",
"version": "6.1.188",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.6.*",
"status": "unaffected",
"version": "6.6.157",
"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",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nocfs2: cluster: don\u0027t 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 -\u003e configfs root\n inode_lock, which can deadlock against subsystem unregistration\n paths taking root -\u003e 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() -\u003e 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."
}
],
"id": "CVE-2026-89491",
"lastModified": "2026-10-19T09:17:42.920",
"metrics": {},
"published": "2026-09-11T20:19:30.943",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/0cbc2f20a6ea7b4a59efa9171b7c694cdd196507"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/3b790774280a610f8bdbd5d4260a07345bcf8e04"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/470212a5eefabcc16b8e2f7fe2844b8737fe571c"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/49002acc520c61002ad195894ac391c94317d3ba"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/4d64f8da82fb9e8dbd5aa9b64c9bb6ac0decea03"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/af09df89db9a68a1d76df0f75667998135bc8d65"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/c9be4de77f97f383b750698e1517fd296041f4bb"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/ce035f208d68b812d83e5482980f2b1c88a9cd94"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.