Skip to content
Threat Brief

← All advisories

CVE-2026-99690

Severity unknownNo known exploitationFix available

ocfs2: cache the mount context for dentry lock callbacks

Record last updated

CVSS score

None

No score published yet

EPSS, chance of exploitation in 30 days

0.2%

Higher than 6% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

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.

Patching and mitigation

Patch status
Fix available (source: CVE record (Linux))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
No vendor link on record

Affected products

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom 3.12.24 before 3.133.13CVE Program
LinuxLinuxfrom 8ed6b23709b346f7bfc1edab47003a205a6a9f69 before a392e0231b9d823f2e62e21fef68ad6145119dcaa392e0231b9d823f2e62e21fef68ad6145119dcaCVE Program
LinuxLinuxfrom 8ed6b23709b346f7bfc1edab47003a205a6a9f69 before ee8997a4521964631d6cc0e511a186f69ce84dbdee8997a4521964631d6cc0e511a186f69ce84dbdCVE Program
LinuxLinuxfrom 8ed6b23709b346f7bfc1edab47003a205a6a9f69 before 85bc2a3b1bece826c908a31c34a4865a80136bee85bc2a3b1bece826c908a31c34a4865a80136beeCVE Program
LinuxLinuxfrom 8ed6b23709b346f7bfc1edab47003a205a6a9f69 before 5b4696e0bfc358619adaeab25ad35b4979af83315b4696e0bfc358619adaeab25ad35b4979af8331CVE Program
LinuxLinux3.15Not documentedCVE Program
LinuxLinuxfc597a301fb2947af29ce67c12a419c39f044975Not documentedCVE Program
LinuxLinux (unaffected)from 6.12.118 up to and including 6.12.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.18.64 up to and including 6.18.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.3.5 up to and including 7.3.*Not documentedCVE Program
LinuxLinux (unaffected)7.4-rc2Not documentedCVE Program
LinuxLinux (unaffected)all versions before 3.15Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (Linux)

    Source: CVE record (Linux) (opens in a new tab)

Vendor guidance and references