ocfs2: cancel dqi_sync_work before freeing oinfo
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 171bf93ce11f4c9929fdce6ce63df8da2f3c4475 · < ef768020366f47d23f39c4f57bcb03af6d1e24b3| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
ocfs2: cancel dqi_sync_work before freeing oinfo
ocfs2_global_read_info() will initialize and schedule dqi_sync_work at the end, if error occurs after successfully reading global quota, it will trigger the following warning with CONFIG_DEBUG_OBJECTS_* enabled:
ODEBUG: free active (active state 0) object: 00000000d8b0ce28 object type: timer_list hint: qsync_work_fn+0x0/0x16c
This reports that there is an active delayed work when freeing oinfo in error handling, so cancel dqi_sync_work first. BTW, return status instead of -1 when .read_file_info fails.
From the CVE record · Linux
In the Linux kernel's ocfs2 quota handling, an error after successfully reading global quota information can leave delayed work active while its associated information is freed. With CONFIG_DEBUG_OBJECTS_* enabled, this triggers an active-timer warning. The input does not describe how an attacker could trigger the error or specify network access, authentication, or user-interaction requirements.
Engineers running Linux kernels with ocfs2 should check their exposure; affected versions are not specified.