ima: Fix use-after-free on a dentry's dname.name
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 2fe5d6def1672ae6635dd71867bf36dcfaa7434b · < a78a6f0da57d058e2009e9958fdcef66f165208c| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ima: Fix use-after-free on a dentry's dname.name
->d_name.name can change on rename and the earlier value can be freed; there are conditions sufficient to stabilize it (->d_lock on dentry, ->d_lock on its parent, ->i_rwsem exclusive on the parent's inode, rename_lock), but none of those are met at any of the sites. Take a stable snapshot of the name instead.
From the CVE record · Linux
Linux kernel IMA code can use a dentry name after a rename changes and frees it. This can result in a use-after-free; the input does not specify an attack path, authentication requirements, or whether user interaction is needed.
Engineers running Linux kernels with IMA should check whether their kernel includes the fix; affected versions are not specified.