CVE-2026-99690
ocfs2: cache the mount context for dentry lock callbacks
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.
Fixes and workarounds
No remediation reported in collected sources.
Missing remediation information is not evidence that no patch exists.
Affected products and versions
| Product | Versions | Authority |
|---|---|---|
| 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) Other versions: unaffected |
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) Other versions: affected |
CNA: Linux |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 3.1 / 7.8 high |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | CNA: Linux |
| 3.1 / 7.8 high |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | NVD: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://git.kernel.org/stable/c/a392e0231b9d823f2e62e21fef68ad6145119dcaCNA: Linux
- https://git.kernel.org/stable/c/ee8997a4521964631d6cc0e511a186f69ce84dbdCNA: Linux
- https://git.kernel.org/stable/c/85bc2a3b1bece826c908a31c34a4865a80136beeCNA: Linux
- https://git.kernel.org/stable/c/5b4696e0bfc358619adaeab25ad35b4979af8331CNA: Linux
- https://git.kernel.org/stable/c/5b4696e0bfc358619adaeab25ad35b4979af8331416baaa9-dc9f-4396-8d5f-8c081fb06d67
- https://git.kernel.org/stable/c/85bc2a3b1bece826c908a31c34a4865a80136bee416baaa9-dc9f-4396-8d5f-8c081fb06d67
- https://git.kernel.org/stable/c/a392e0231b9d823f2e62e21fef68ad6145119dca416baaa9-dc9f-4396-8d5f-8c081fb06d67
- https://git.kernel.org/stable/c/ee8997a4521964631d6cc0e511a186f69ce84dbd416baaa9-dc9f-4396-8d5f-8c081fb06d67
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.