From: Greg KH <gregkh@linuxfoundation.org>
To: SeongJae Park <sj@kernel.org>
Cc: Alon Zahavi <zahavi.alon@gmail.com>,
almaz.alexandrovich@paragon-software.com, ntfs3@lists.linux.dev,
linux-kernel@vger.kernel.org, Tal Lossos <tallossos@gmail.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] ntfs3: Fix attr_punch_hole() null pointer derenference
Date: Sun, 22 Jan 2023 14:46:25 +0100 [thread overview]
Message-ID: <Y80+MZLA2sXyYf2J@kroah.com> (raw)
In-Reply-To: <20230117202136.116810-1-sj@kernel.org>
On Tue, Jan 17, 2023 at 08:21:36PM +0000, SeongJae Park wrote:
> Hello,
>
> On Mon, 15 Aug 2022 14:07:12 +0300 Alon Zahavi <zahavi.alon@gmail.com> wrote:
>
> > From: Alon Zahavi <zahavi.alon@gmail.com>
> >
> > The bug occours due to a misuse of `attr` variable instead of `attr_b`.
> > `attr` is being initialized as NULL, then being derenfernced
> > as `attr->res.data_size`.
> >
> > This bug causes a crash of the ntfs3 driver itself,
> > If compiled directly to the kernel, it crashes the whole system.
> >
> > Signed-off-by: Alon Zahavi <zahavi.alon@gmail.com>
> > Co-developed-by: Tal Lossos <tallossos@gmail.com>
> > Signed-off-by: Tal Lossos <tallossos@gmail.com>
>
> This patch has now merged in mainline as
> 6d5c9e79b726cc473d40e9cb60976dbe8e669624. stable@, could you please merge this
> in stable kernels?
>
> Fixes: be71b5cba2e64 ("fs/ntfs3: Add attrib operations") # 5.14
>
Now queued up, thanks.
greg k-h
next prev parent reply other threads:[~2023-01-22 13:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 11:07 [PATCH] ntfs3: Fix attr_punch_hole() null pointer derenference Alon Zahavi
2022-09-30 15:44 ` Konstantin Komarov
2023-01-17 20:21 ` SeongJae Park
2023-01-17 20:21 ` SeongJae Park
2023-01-22 13:46 ` Greg KH [this message]
2023-01-17 20:27 ` SeongJae Park
2023-01-17 20:27 ` SeongJae Park
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=Y80+MZLA2sXyYf2J@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
--cc=sj@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tallossos@gmail.com \
--cc=zahavi.alon@gmail.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 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.