inotify: Avoid reporting event with invalid wd
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 7e790dd5fc937bc8d2400c30a05e32a9e9eef276 · < a48bacee05860c6089c3482bcdc80720b0ee5732| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
inotify: Avoid reporting event with invalid wd
When inotify_freeing_mark() races with inotify_handle_inode_event() it can happen that inotify_handle_inode_event() sees that i_mark->wd got already reset to -1 and reports this value to userspace which can confuse the inotify listener. Avoid the problem by validating that wd is sensible (and pretend the mark got removed before the event got generated otherwise).
From the CVE record · Linux
A race in the Linux kernel's inotify code can report an invalid watch descriptor (-1) to userspace, confusing an inotify listener. The input does not describe an attacker capability or specify network access, authentication, or user-interaction conditions.
Engineers running the Linux kernel should check their versions; affected versions are not specified.