From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Shaoying Xu <shaoyi@amazon.com>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.4 2/2] ext4: fix slab-use-after-free in ext4_split_extent_at()
Date: Sat, 25 Jan 2025 09:03:46 -0500 [thread overview]
Message-ID: <20250124205321-d47ea8205bb009a1@stable.kernel.org> (raw)
In-Reply-To: <20250125003135.11978-3-shaoyi@amazon.com>
[ Sasha's backport helper bot ]
Hi,
The upstream commit SHA1 provided is correct: c26ab35702f8cd0cdc78f96aa5856bfb77be798f
WARNING: Author mismatch between patch and upstream commit:
Backport author: Shaoying Xu<shaoyi@amazon.com>
Commit author: Baokun Li<libaokun1@huawei.com>
Status in newer kernel trees:
6.12.y | Present (exact SHA1)
6.6.y | Present (different SHA1: 8fe117790b37)
6.1.y | Present (different SHA1: a5401d4c3e2a)
5.15.y | Present (different SHA1: cafcc1bd6293)
5.10.y | Present (different SHA1: e52f933598b7)
5.4.y | Not found
Note: The patch differs from the upstream commit:
---
1: c26ab35702f8c ! 1: 2df1566f67dbb ext4: fix slab-use-after-free in ext4_split_extent_at()
@@ Metadata
## Commit message ##
ext4: fix slab-use-after-free in ext4_split_extent_at()
+ [ Upstream commit c26ab35702f8cd0cdc78f96aa5856bfb77be798f ]
+
We hit the following use-after-free:
==================================================================
@@ Commit message
Tested-by: Ojaswin Mujoo <ojaswin@linux.ibm.com>
Link: https://patch.msgid.link/20240822023545.1994557-4-libaokun@huaweicloud.com
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
+ Signed-off-by: Shaoying Xu <shaoyi@amazon.com>
## fs/ext4/extents.c ##
@@ fs/ext4/extents.c: static int ext4_split_extent_at(handle_t *handle,
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-5.4.y | Success | Success |
prev parent reply other threads:[~2025-01-25 14:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-25 0:31 [PATCH 5.4 0/2] CVE-2024-49884 Shaoying Xu
2025-01-25 0:31 ` [PATCH 5.4 1/2] ext4: avoid ext4_error()'s caused by ENOMEM in the truncate path Shaoying Xu
2025-01-25 14:03 ` Sasha Levin
2025-01-25 0:31 ` [PATCH 5.4 2/2] ext4: fix slab-use-after-free in ext4_split_extent_at() Shaoying Xu
2025-01-25 14:03 ` Sasha Levin [this message]
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=20250124205321-d47ea8205bb009a1@stable.kernel.org \
--to=sashal@kernel.org \
--cc=shaoyi@amazon.com \
--cc=stable@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.