ocfs2: cache the mount context for dentry lock callbacks
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel ee8997a4521964631d6cc0e511a186f69ce84dbd, Kernel 3.13, Kernel 5b4696e0bfc358619adaeab25ad35b4979af8331 and 5 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=8ed6b23709b346f7bfc1edab47003a205a6a9f69 <ee8997a4521964631d6cc0e511a186f69ce84dbd, >=3.12.24 <3.13, >=8ed6b23709b346f7bfc1edab47003a205a6a9f69 <5b4696e0bfc358619adaeab25ad35b4979af8331, >=8ed6b23709b346f7bfc1edab47003a205a6a9f69 <85bc2a3b1bece826c908a31c34a4865a80136bee, >=8ed6b23709b346f7bfc1edab47003a205a6a9f69 <a392e0231b9d823f2e62e21fef68ad6145119dca, =3.15, =fc597a301fb2947af29ce67c12a419c39f044975 | ee8997a4521964631d6cc0e511a186f69ce84dbd, 3.13, 5b4696e0bfc358619adaeab25ad35b4979af8331, 85bc2a3b1bece826c908a31c34a4865a80136bee, a392e0231b9d823f2e62e21fef68ad6145119dca |
| linux-kernel: Kernel | >=3.15.0 <6.12.118, >=6.13.0 <6.18.64, >=6.19.0 <7.3.5, >=3.12.24 <3.13 | 6.12.118, 6.18.64, 7.3.5, 3.13 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket