# CVE-2026-99690: ocfs2: cache the mount context for dentry lock callbacks

Status: published. Published: 2026-11-20. Updated: 2026-11-22.

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

ocfs2: cache the mount context for dentry lock callbacks

ocfs2_drop_dentry_lock() drops the inode reference before releasing the
DENTRY lock.  This lets inode eviction release the local inode and open
locks before a remote unlink can proceed past the DENTRY lock.

A DLM callback can still arrive before the DENTRY lock has been dropped.
ocfs2_get_dentry_osb() obtains the mount context through dl_inode->i_sb,
which can access a freed inode when the downconvert thread drops the
last inode reference in its post-unlock callback:

  Downconvert thread                     DLM callback thread
  ------------------                     -------------------
  ocfs2_process_blocked_lock()
    ocfs2_dentry_post_unlock()
      ocfs2_dentry_lock_put()
        ocfs2_drop_dentry_lock()
          iput(dl->dl_inode)
          [inode reclaimed after RCU]
                                         ocfs2_blocking_ast()
                                           ocfs2_get_dentry_osb()
                                             dl->dl_inode->i_sb
          ocfs2_simple_drop_lockres()

Store the mount context in the DENTRY lock resource's l_priv field and use
the default mount-context lookup.  Recover the containing dentry lock with
container_of(), as already done for refcount locks, and remove
ocfs2_get_dentry_osb().  ocfs2_dismount_volume() shuts down the DLM before
freeing the mount context, so callbacks can use it without accessing the
inode.  Preserve the existing iput-before-unlock order to avoid delaying
local inode and open lock release until after the DENTRY lock is released.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Linux / Linux: ≥ 8ed6b23709b346f7bfc1edab47003a205a6a9f69; < a392e0231b9d823f2e62e21fef68ad6145119dca (affected, git); ≥ 8ed6b23709b346f7bfc1edab47003a205a6a9f69; < ee8997a4521964631d6cc0e511a186f69ce84dbd (affected, git); ≥ 8ed6b23709b346f7bfc1edab47003a205a6a9f69; < 85bc2a3b1bece826c908a31c34a4865a80136bee (affected, git); ≥ 8ed6b23709b346f7bfc1edab47003a205a6a9f69; < 5b4696e0bfc358619adaeab25ad35b4979af8331 (affected, git); fc597a301fb2947af29ce67c12a419c39f044975 (affected, git); ≥ 3.12.24; < 3.13 (affected, semver). Source: CNA: Linux
- Linux / Linux: 3.15 (affected); ≥ 0; < 3.15 (unaffected, semver); ≥ 6.12.118; ≤ 6.12.* (unaffected, semver); ≥ 6.18.64; ≤ 6.18.* (unaffected, semver); ≥ 7.3.5; ≤ 7.3.* (unaffected, semver); ≥ 7.4-rc2; ≤ * (unaffected, original_commit_for_fix). Source: CNA: Linux

## Severity and prioritization

- CVSS 3.1: 7.8 (high); CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H; source: CNA: Linux

- CVSS 3.1: 7.8 (high); CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H; source: NVD: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

- CISA KEV: No listing in collected sources

- EPSS: 0.17% as of 2026-11-21; percentile 6.19%

- SSVC: Not available

- Weaknesses: Not reported

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://git.kernel.org/stable/c/a392e0231b9d823f2e62e21fef68ad6145119dca (CNA: Linux)

- https://git.kernel.org/stable/c/ee8997a4521964631d6cc0e511a186f69ce84dbd (CNA: Linux)

- https://git.kernel.org/stable/c/85bc2a3b1bece826c908a31c34a4865a80136bee (CNA: Linux)

- https://git.kernel.org/stable/c/5b4696e0bfc358619adaeab25ad35b4979af8331 (CNA: Linux)

- https://git.kernel.org/stable/c/5b4696e0bfc358619adaeab25ad35b4979af8331 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/85bc2a3b1bece826c908a31c34a4865a80136bee (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/a392e0231b9d823f2e62e21fef68ad6145119dca (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/ee8997a4521964631d6cc0e511a186f69ce84dbd (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

## Provenance

- CNA: Linux: https://www.cve.org/CVERecord?id=CVE-2026-99690; retrieved 2026-11-22; source updated 2026-11-22

- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-99690; retrieved 2026-11-22; source updated 2026-11-22

- FIRST EPSS: https://api.first.org/data/v1/epss?cve=CVE-2026-99690; retrieved 2026-11-22; source updated Not reported

Revision: f5cf26c50b285a56aee38b3b4c72b353b5249076aad228063101905b36caffdf

Canonical: https://y2.dev/cve/CVE-2026-99690

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.