Skip to main content
No exploitation reportedFix availableAwaiting NVD analysis

CVE-2026-99690

ocfs2: cache the mount context for dentry lock callbacks

No exploitation reported by the sources we read.

  • Published2026-11-20
  • Fixed in7.3.5 · 6.18.64 · 6.12.118 · 3.13

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC
  1. 2026-11-2005:50CVE publishedCNA

Versions per branch

OSV
Linux kernel
BranchAffectedFixed in
7.3≥ 6.19.0, < 7.3.57.3.5
6.x≥ 6.13.0, < 6.18.646.18.64
6.12≥ 3.15.0, < 6.12.1186.12.118
3.x≥ 3.12.24, < 3.133.13

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA2 products

As Linux, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • Linuxother versions: not affected

    https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

    Affected
    • ≥ 8ed6b23709b346f7bfc1edab47003a205a6a9f69, < a392e0231b9d823f2e62e21fef68ad6145119dcafixed in a392e0231b9d823f2e62e21fef68ad6145119dcagit
    • ≥ 8ed6b23709b346f7bfc1edab47003a205a6a9f69, < ee8997a4521964631d6cc0e511a186f69ce84dbdfixed in ee8997a4521964631d6cc0e511a186f69ce84dbdgit
    • ≥ 8ed6b23709b346f7bfc1edab47003a205a6a9f69, < 85bc2a3b1bece826c908a31c34a4865a80136beefixed in 85bc2a3b1bece826c908a31c34a4865a80136beegit
    • ≥ 8ed6b23709b346f7bfc1edab47003a205a6a9f69, < 5b4696e0bfc358619adaeab25ad35b4979af8331fixed in 5b4696e0bfc358619adaeab25ad35b4979af8331git
    • = fc597a301fb2947af29ce67c12a419c39f044975no fix statedgit
    • ≥ 3.12.24, < 3.13fixed in 3.13semver
  • Linuxother versions: affected

    https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

    Affected
    • = 3.15no fix stated

    Not affected < 3.15 · ≥ 6.12.118, ≤ 6.12.* · ≥ 6.18.64, ≤ 6.18.* · ≥ 7.3.5, ≤ 7.3.* · ≥ 7.4-rc2

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE terms of useCVE recordupdated 2026-11-20

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • kernelAzure Linux:3all versions · no fixed version listed
  • linuxDebian:14all versions · no fixed version listed
  • linuxDebian:13all versions · fixed in 6.12.118-1
  • linuxDebian:12all versions · no fixed version listed
  • linux-ltsAlpaquita:streamfrom 6.18.62-r0 · fixed in 6.18.64-r0
  • linux-ltsAlpaquita:25from 6.12.115-r0 · no fixed version listed
  • linux-ltsAlpaquita:23from 6.1.191-r1 · no fixed version listed

Vendor advisories

  • CVE-2026-99690 Red Hat Product Security

    kernel: kernel: Denial of Service via use-after-free in OCFS2 lock callbacks

Full record on NVD

Fix

  1. Update Linux kernel to 7.3.5 · 6.18.64 · 6.12.118 · 3.13

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Published
2026-11-20
Last modified
2026-11-22
NVD status
Received
GitHub advisory
GHSA-2w86-w8w2-685q

Frequently asked questions

What is CVE-2026-99690?

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.

Is CVE-2026-99690 actively exploited?

Active exploitation of CVE-2026-99690 has not been confirmed. Its EPSS score was 0.2% on 2026-11-21, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-99690?

CVE-2026-99690 has a CVSS v3 base score of 7.8 (High severity), with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

Running Linux kernel? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website checks · 250 API requests/month

Sources for this record