ocfs2: free inode when ocfs2_get_init_inode() fails
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 9c89fe0af826bfff36d8019ea6fd78db09b3c478 · < 03db61c43c8e2729896fda6b9a95c7fb5c875c20| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ocfs2: free inode when ocfs2_get_init_inode() fails
syzbot is reporting busy inodes after unmount, for commit 9c89fe0af826 ("ocfs2: Handle error from dquot_initialize()") forgot to call iput() when new_inode() succeeded and dquot_initialize() failed.
From the CVE record · Linux
The Linux kernel's ocfs2 code fails to release an inode when new_inode() succeeds but dquot_initialize() fails. This can leave busy inodes after unmount. The input does not establish an attacker path, authentication requirements, or user-interaction requirements.
Engineers running Linux kernels with ocfs2 should check whether their kernel includes the affected change; affected versions are not specified.