From: Luiz Capitulino <luizcap@amazon.com>
To: <stable@vger.kernel.org>
Subject: [6.1.y] Please apply 98bea253aa28ad8be2ce565a9ca21beb4a9419e5
Date: Thu, 1 Jun 2023 17:17:54 -0400 [thread overview]
Message-ID: <23bb697e-c965-8321-f648-03f804853cdb@amazon.com> (raw)
It fixes CVE-2022-48425 and is applied to 5.15.y and 6.3.y. I quickly tested
the commit by mounting an NTFS partition and building a kernel in it.
"""
commit 98bea253aa28ad8be2ce565a9ca21beb4a9419e5
Author: Edward Lo <edward.lo@ambergroup.io>
Date: Sat Nov 5 23:39:44 2022 +0800
fs/ntfs3: Validate MFT flags before replaying logs
"""
Thanks,
- Luiz
next reply other threads:[~2023-06-01 21:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 21:17 Luiz Capitulino [this message]
2023-06-06 14:56 ` [6.1.y] Please apply 98bea253aa28ad8be2ce565a9ca21beb4a9419e5 Luiz Capitulino
2023-06-06 16:22 ` Greg KH
2023-06-06 16:27 ` Luiz Capitulino
2023-06-07 12:47 ` Greg KH
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=23bb697e-c965-8321-f648-03f804853cdb@amazon.com \
--to=luizcap@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