CVE-2026-89491

UNRATEDCVSS · not yet scoredTrending — 4 sources updated this week
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

ocfs2: cluster: don't sleep while holding o2hb_live_lock in o2hb_region_pin()

Patch series "ocfs2: cluster: o2hb_region_pin() fixes", v2.

This series fixes three related issues in o2hb_region_pin(), all are from the original implementation in commit: 58a3158a5d17 ("ocfs2/cluster: Pin/unpin o2hb regions"):

1) It is called with o2hb_live_lock (a spinlock) held, but the underlying configfs_depend_item() sleeps (takes inode rwsem and pins the filesystem). This triggers BUG under CONFIG_DEBUG_ATOMIC_SLEEP.

2) When called from the configfs drop_item callback, it creates a lock order inversion: parent inode_lock -> configfs root inode_lock, which can deadlock against subsystem unregistration paths taking root -> parent.

3) If pinning fails partway through o2hb_region_inc_user(), the o2hb_dependent_users counter is leaked and partially-pinned regions are never released, leaving heartbeat regions unprotected on subsequent mounts.

Patch 1 reworks o2hb_region_pin() to drop o2hb_live_lock across each sleeping configfs_depend_item() call, using a config_item reference to keep the region alive while unlocked.

Patch 2 adds a from_callback parameter to select configfs_depend_item_unlocked() when called from configfs context, avoiding the inode_lock nesting.

Patch 3 fixes the error path in o2hb_region_inc_user() to unpin and decrement the counter on failure.

This patch (of 3):

o2hb_region_pin() is always called with the o2hb_live_lock spinlock held (from o2hb_region_inc_user() and o2hb_heartbeat_group_drop_item()), but it calls o2nm_depend_item() -> configfs_depend_item(), which sleeps: it pins the configfs filesystem and takes the configfs root inode rwsem. Under CONFIG_DEBUG_ATOMIC_SLEEP this triggers:

BUG: sleeping function called from invalid context at kernel/locking/rwsem.c in_atomic(): 1, ... name: mount.ocfs2 down_write configfs_depend_item o2hb_region_pin o2hb_region_inc_user o2hb_register_callback dlm_register_domain_handlers ... ocfs2_dlm_init ocfs2_mount_volume ocfs2_fill_super

Rework o2hb_region_pin() to pin one region at a time with the lock dropped across the sleeping call: under o2hb_live_lock find the next eligible region and take a config_item reference to keep it alive, drop the lock, call o2nm_depend_item(), then retake the lock and record the pin. The config_item_put() is done with the lock released as well, since o2hb_region_release() also acquires o2hb_live_lock and can sleep. The region list may change while unlocked, so the scan restarts from the top after each pin. Local heartbeat still pins only the matching region; global heartbeat pins all eligible regions.

The unpin path is unaffected: configfs_undepend_item() only takes a spinlock and does not sleep.

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.2%
EPSS %ILE
11th
KEV
Not listed

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 11, 2026

Last Modified

September 14, 2026

Vendor Advisories for CVE-2026-89491(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (360 versions)
  • every version on: no fix on record
—
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1
  • every version up to 6.12.111-1~deb12u1: fixed in 6.12.111-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (35 versions)
  • every version up to 6.12.111-1: fixed in 6.12.111-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (179 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 13× in last 7d / 53× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  2. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  3. 2026-10-12 14:48 UTCEG score recompute
  4. 2026-10-11 19:15 UTCEG score recompute
  5. 2026-10-11 16:32 UTCEG score recompute
  6. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  7. 2026-10-11 13:47 UTCEG score recompute
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  10. 2026-10-08 23:26 UTCVendor advisory
  11. 2026-10-08 23:26 UTCGHSA enrichmentGHSA-r32m-fj66-qf6p
  12. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  13. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  14. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  15. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  16. 2026-10-05 16:51 UTCVendor advisory
  17. 2026-10-05 16:51 UTCGHSA enrichmentGHSA-r32m-fj66-qf6p
  18. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  19. 2026-10-02 16:25 UTCVendor advisory
  20. 2026-10-02 16:24 UTCGHSA enrichmentGHSA-r32m-fj66-qf6p
  21. 2026-10-02 16:24 UTCVendor advisory
  22. 2026-10-02 16:24 UTCGHSA enrichmentGHSA-r32m-fj66-qf6p
  23. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  24. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  25. 2026-09-29 15:54 UTCEG score recompute
Show 33 more
  1. 2026-09-29 15:54 UTCVendor advisory
  2. 2026-09-29 15:54 UTCGHSA enrichmentGHSA-r32m-fj66-qf6p
  3. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  4. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  5. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  6. 2026-09-26 15:22 UTCVendor advisory
  7. 2026-09-26 15:22 UTCGHSA enrichmentGHSA-r32m-fj66-qf6p
  8. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  9. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  10. 2026-09-23 14:55 UTCVendor advisory
  11. 2026-09-23 14:55 UTCGHSA enrichmentGHSA-r32m-fj66-qf6p
  12. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  13. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  14. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  15. 2026-09-20 14:28 UTCVendor advisory
  16. 2026-09-20 14:28 UTCGHSA enrichmentGHSA-r32m-fj66-qf6p
  17. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  18. 2026-09-17 19:32 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  19. 2026-09-17 14:01 UTCVendor advisory
  20. 2026-09-17 14:01 UTCGHSA enrichmentGHSA-r32m-fj66-qf6p
  21. 2026-09-16 14:09 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  22. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  23. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  24. 2026-09-14 13:34 UTCGHSA enrichmentGHSA-r32m-fj66-qf6p
  25. 2026-09-14 13:27 UTCNVD update
  26. 2026-09-14 12:30 UTCEG score recompute
  27. 2026-09-14 12:30 UTCGHSA enrichmentGHSA-r32m-fj66-qf6p
  28. 2026-09-14 12:24 UTCMITRE cvelistV5
  29. 2026-09-13 16:48 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  30. 2026-09-12 15:02 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  31. 2026-09-11 20:36 UTCNVD update
  32. 2026-09-11 19:51 UTCEG score recompute
  33. 2026-09-11 19:49 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-89491?
CVE-2026-89491 is a vulnerability whose severity is not yet rated; its CVE record was published on September 11, 2026. In the Linux kernel, the following vulnerability has been resolved: ocfs2: cluster: don't sleep while holding o2hblivelock in o2hbregionpin() Patch series "ocfs2: cluster: o2hbregionpin() fixes", v2. This series fixes three related issues in o2hbregionpin(), all are from the original implementation…
When was the CVE record for CVE-2026-89491 published?
The CVE record for CVE-2026-89491 was published on September 11, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 14, 2026; the record at its source may have been updated since.
Is CVE-2026-89491 actively exploited?
CVE-2026-89491 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (11th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-89491?
A fix for CVE-2026-89491 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-89491 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-89491

Explore →

Is Your Infrastructure Affected by CVE-2026-89491?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.