From: Jan Kara <jack@suse.cz>
To: libaokun@huaweicloud.com
Cc: linux-ext4@vger.kernel.org, tytso@mit.edu,
adilger.kernel@dilger.ca, jack@suse.cz, ritesh.list@gmail.com,
linux-kernel@vger.kernel.org, yi.zhang@huawei.com,
yangerkun@huawei.com, Baokun Li <libaokun1@huawei.com>
Subject: Re: [PATCH 06/20] ext4: avoid use-after-free in ext4_ext_show_leaf()
Date: Wed, 24 Jul 2024 21:16:04 +0200 [thread overview]
Message-ID: <20240724191604.6grmtu4t7gmvtlec@quack3> (raw)
In-Reply-To: <20240710040654.1714672-7-libaokun@huaweicloud.com>
On Wed 10-07-24 12:06:40, libaokun@huaweicloud.com wrote:
> From: Baokun Li <libaokun1@huawei.com>
>
> In ext4_find_extent(), path may be freed by error or be reallocated, so
> using a previously saved *ppath may have been freed and thus may trigger
> use-after-free, as follows:
>
> ext4_split_extent
> path = *ppath;
> ext4_split_extent_at(ppath)
> path = ext4_find_extent(ppath)
> ext4_split_extent_at(ppath)
> // ext4_find_extent fails to free path
> // but zeroout succeeds
> ext4_ext_show_leaf(inode, path)
> eh = path[depth].p_hdr
> // path use-after-free !!!
>
> Similar to ext4_split_extent_at(), we use *ppath directly as an input to
> ext4_ext_show_leaf(). Fix a spelling error by the way.
>
> Same problem in ext4_ext_handle_unwritten_extents(). Since 'path' is only
> used in ext4_ext_show_leaf(), remove 'path' and use *ppath directly.
>
> This issue is triggered only when EXT_DEBUG is defined and therefore does
> not affect functionality.
>
> Signed-off-by: Baokun Li <libaokun1@huawei.com>
Looks good. Feel free to add:
Reviewed-by: Jan Kara <jack@suse.cz>
I'd just note that this shows that modifying ppath in the called function
was not a great idea as it makes possible use-after-free issues due to
cached values being used very hard to spot and very easy to introduce...
Honza
> ---
> fs/ext4/extents.c | 9 ++++-----
> 1 file changed, 4 insertions(+), 5 deletions(-)
>
> diff --git a/fs/ext4/extents.c b/fs/ext4/extents.c
> index 3a70a0739af8..1660434fbfc7 100644
> --- a/fs/ext4/extents.c
> +++ b/fs/ext4/extents.c
> @@ -3328,7 +3328,7 @@ static int ext4_split_extent_at(handle_t *handle,
> }
>
> /*
> - * ext4_split_extents() splits an extent and mark extent which is covered
> + * ext4_split_extent() splits an extent and mark extent which is covered
> * by @map as split_flags indicates
> *
> * It may result in splitting the extent into multiple extents (up to three)
> @@ -3404,7 +3404,7 @@ static int ext4_split_extent(handle_t *handle,
> goto out;
> }
>
> - ext4_ext_show_leaf(inode, path);
> + ext4_ext_show_leaf(inode, *ppath);
> out:
> return err ? err : allocated;
> }
> @@ -3869,14 +3869,13 @@ ext4_ext_handle_unwritten_extents(handle_t *handle, struct inode *inode,
> struct ext4_ext_path **ppath, int flags,
> unsigned int allocated, ext4_fsblk_t newblock)
> {
> - struct ext4_ext_path __maybe_unused *path = *ppath;
> int ret = 0;
> int err = 0;
>
> ext_debug(inode, "logical block %llu, max_blocks %u, flags 0x%x, allocated %u\n",
> (unsigned long long)map->m_lblk, map->m_len, flags,
> allocated);
> - ext4_ext_show_leaf(inode, path);
> + ext4_ext_show_leaf(inode, *ppath);
>
> /*
> * When writing into unwritten space, we should not fail to
> @@ -3973,7 +3972,7 @@ ext4_ext_handle_unwritten_extents(handle_t *handle, struct inode *inode,
> if (allocated > map->m_len)
> allocated = map->m_len;
> map->m_len = allocated;
> - ext4_ext_show_leaf(inode, path);
> + ext4_ext_show_leaf(inode, *ppath);
> out2:
> return err ? err : allocated;
> }
> --
> 2.39.2
>
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2024-07-24 19:16 UTC|newest]
Thread overview: 84+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-10 4:06 [PATCH 00/20] ext4: some bugfixes and cleanups for ext4 extents path libaokun
2024-07-10 4:06 ` [PATCH 01/20] ext4: refactor ext4_ext_rm_idx() to index 'path' libaokun
2024-07-24 18:44 ` Jan Kara
2024-07-25 9:14 ` Ojaswin Mujoo
2024-07-10 4:06 ` [PATCH 02/20] ext4: prevent partial update of the extents path libaokun
2024-07-14 15:42 ` Ojaswin Mujoo
2024-07-15 12:33 ` Baokun Li
2024-07-15 12:41 ` Baokun Li
2024-07-16 9:54 ` Ojaswin Mujoo
2024-07-16 11:54 ` Baokun Li
2024-07-17 5:29 ` Ojaswin Mujoo
2024-07-17 6:11 ` Baokun Li
2024-07-24 6:23 ` Ojaswin Mujoo
2024-07-25 5:35 ` Baokun Li
2024-07-25 8:48 ` Ojaswin Mujoo
2024-07-24 18:53 ` Jan Kara
2024-07-10 4:06 ` [PATCH 03/20] ext4: fix double brelse() the buffer " libaokun
2024-07-24 19:01 ` Jan Kara
2024-07-26 11:45 ` Ojaswin Mujoo
2024-07-30 8:47 ` Baokun Li
2024-08-01 6:26 ` Ojaswin Mujoo
2024-07-10 4:06 ` [PATCH 04/20] ext4: add new ext4_ext_path_brelse() helper libaokun
2024-07-24 19:02 ` Jan Kara
2024-07-26 11:53 ` Ojaswin Mujoo
2024-07-10 4:06 ` [PATCH 05/20] ext4: fix slab-use-after-free in ext4_split_extent_at() libaokun
2024-07-24 19:13 ` Jan Kara
2024-07-27 10:36 ` Ojaswin Mujoo
2024-07-30 8:57 ` Baokun Li
2024-07-30 9:26 ` Ojaswin Mujoo
2024-07-10 4:06 ` [PATCH 06/20] ext4: avoid use-after-free in ext4_ext_show_leaf() libaokun
2024-07-24 19:16 ` Jan Kara [this message]
2024-07-25 5:41 ` Baokun Li
2024-07-27 10:43 ` Ojaswin Mujoo
2024-07-10 4:06 ` [PATCH 07/20] ext4: drop ppath from ext4_ext_replay_update_ex() to avoid double-free libaokun
2024-07-25 10:31 ` Jan Kara
2024-07-27 11:18 ` Ojaswin Mujoo
2024-07-10 4:06 ` [PATCH 08/20] ext4: get rid of ppath in ext4_find_extent() libaokun
2024-07-25 10:38 ` Jan Kara
2024-07-27 6:18 ` Baokun Li
2024-07-29 11:28 ` Jan Kara
2024-07-30 10:03 ` Ojaswin Mujoo
2024-07-10 4:06 ` [PATCH 09/20] ext4: get rid of ppath in get_ext_path() libaokun
2024-07-25 10:41 ` Jan Kara
2024-08-01 7:16 ` Ojaswin Mujoo
2024-07-10 4:06 ` [PATCH 10/20] ext4: get rid of ppath in ext4_ext_create_new_leaf() libaokun
2024-07-25 10:46 ` Jan Kara
2024-07-27 6:35 ` Baokun Li
2024-08-02 7:34 ` Ojaswin Mujoo
2024-08-02 13:07 ` Baokun Li
2024-07-10 4:06 ` [PATCH 11/20] ext4: get rid of ppath in ext4_ext_insert_extent() libaokun
2024-07-25 10:59 ` Jan Kara
2024-08-02 8:01 ` Ojaswin Mujoo
2024-07-10 4:06 ` [PATCH 12/20] ext4: get rid of ppath in ext4_split_extent_at() libaokun
2024-07-25 11:07 ` Jan Kara
2024-07-27 6:42 ` Baokun Li
2024-08-21 3:19 ` Theodore Ts'o
2024-08-21 3:29 ` Baokun Li
2024-08-02 8:12 ` Ojaswin Mujoo
2024-07-10 4:06 ` [PATCH 13/20] ext4: get rid of ppath in ext4_force_split_extent_at() libaokun
2024-07-25 11:14 ` Jan Kara
2024-08-02 20:01 ` Ojaswin Mujoo
2024-08-03 2:23 ` Baokun Li
2024-07-10 4:06 ` [PATCH 14/20] ext4: get rid of ppath in ext4_split_extent() libaokun
2024-07-25 12:07 ` Jan Kara
2024-08-02 20:17 ` Ojaswin Mujoo
2024-07-10 4:06 ` [PATCH 15/20] ext4: get rid of ppath in ext4_split_convert_extents() libaokun
2024-07-25 12:12 ` Jan Kara
2024-08-02 20:26 ` Ojaswin Mujoo
2024-07-10 4:06 ` [PATCH 16/20] ext4: get rid of ppath in ext4_convert_unwritten_extents_endio() libaokun
2024-07-25 12:14 ` Jan Kara
2024-08-02 20:28 ` Ojaswin Mujoo
2024-07-10 4:06 ` [PATCH 17/20] ext4: get rid of ppath in ext4_ext_convert_to_initialized() libaokun
2024-07-25 12:18 ` Jan Kara
2024-08-02 20:38 ` Ojaswin Mujoo
2024-07-10 4:06 ` [PATCH 18/20] ext4: get rid of ppath in ext4_ext_handle_unwritten_extents() libaokun
2024-07-25 12:22 ` Jan Kara
2024-08-02 20:44 ` Ojaswin Mujoo
2024-07-10 4:06 ` [PATCH 19/20] ext4: get rid of ppath in convert_initialized_extent() libaokun
2024-07-25 12:23 ` Jan Kara
2024-08-02 20:46 ` Ojaswin Mujoo
2024-07-10 4:06 ` [PATCH 20/20] ext4: avoid unnecessary extent path frees and allocations libaokun
2024-07-25 12:31 ` Jan Kara
2024-08-02 20:58 ` Ojaswin Mujoo
2024-07-25 9:02 ` [PATCH 00/20] ext4: some bugfixes and cleanups for ext4 extents path Ojaswin Mujoo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240724191604.6grmtu4t7gmvtlec@quack3 \
--to=jack@suse.cz \
--cc=adilger.kernel@dilger.ca \
--cc=libaokun1@huawei.com \
--cc=libaokun@huaweicloud.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ritesh.list@gmail.com \
--cc=tytso@mit.edu \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox