From: Shaoying Xu <shaoyi@amazon.com>
To: <stable@vger.kernel.org>
Cc: <shaoyi@amazon.com>
Subject: [PATCH 5.4 0/2] CVE-2024-49884
Date: Sat, 25 Jan 2025 00:31:33 +0000 [thread overview]
Message-ID: <20250125003135.11978-1-shaoyi@amazon.com> (raw)
Backport CVE-2024-49884 fixes to stable 5.4.
Baokun Li (1):
ext4: fix slab-use-after-free in ext4_split_extent_at()
Theodore Ts'o (1):
ext4: avoid ext4_error()'s caused by ENOMEM in the truncate path
fs/ext4/ext4.h | 1 +
fs/ext4/extents.c | 64 +++++++++++++++++++++++++++++++++++++++--------
2 files changed, 54 insertions(+), 11 deletions(-)
--
2.40.1
next reply other threads:[~2025-01-25 0:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-25 0:31 Shaoying Xu [this message]
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
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=20250125003135.11978-1-shaoyi@amazon.com \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).