diff options
author | Jann Horn <jannh@google.com> | 2024-11-18 17:33:13 +0100 |
---|---|---|
committer | Jan Kara <jack@suse.cz> | 2024-11-18 17:33:13 +0100 |
commit | 21d1b618b6b9da46c5116c640ac4b1cc8d40d63a (patch) | |
tree | 9359bcb968a59530fb9b17ee85d1e48c6b36b500 /security | |
parent | fsnotify: fix sending inotify event with unexpected filename (diff) | |
download | linux-21d1b618b6b9da46c5116c640ac4b1cc8d40d63a.tar.xz linux-21d1b618b6b9da46c5116c640ac4b1cc8d40d63a.zip |
fsnotify: Fix ordering of iput() and watched_objects decrement
Ensure the superblock is kept alive until we're done with iput().
Holding a reference to an inode is not allowed unless we ensure the
superblock stays alive, which fsnotify does by keeping the
watched_objects count elevated, so iput() must happen before the
watched_objects decrement.
This can lead to a UAF of something like sb->s_fs_info in tmpfs, but the
UAF is hard to hit because race orderings that oops are more likely, thanks
to the CHECK_DATA_CORRUPTION() block in generic_shutdown_super().
Also, ensure that fsnotify_put_sb_watched_objects() doesn't call
fsnotify_sb_watched_objects() on a superblock that may have already been
freed, which would cause a UAF read of sb->s_fsnotify_info.
Cc: stable@kernel.org
Fixes: d2f277e26f52 ("fsnotify: rename fsnotify_{get,put}_sb_connectors()")
Signed-off-by: Jann Horn <jannh@google.com>
Signed-off-by: Jan Kara <jack@suse.cz>
Diffstat (limited to 'security')
0 files changed, 0 insertions, 0 deletions