From: Greg KH <gregkh@linuxfoundation.org>
To: Zheng Wang <zyytlz.wz@163.com>
Cc: stable@vger.kernel.org, hackerzheng666@gmail.com,
sashal@kernel.org, patches@lists.linux.dev,
amergnat@baylibre.com, wenst@chromium.org,
angelogioacchino.delregno@collabora.com,
hverkuil-cisco@xs4all.nl
Subject: Re: [RESEND PATCH v2] media: mtk-jpeg: Fix use after free bug due to uncanceled work
Date: Thu, 12 Oct 2023 19:23:53 +0200 [thread overview]
Message-ID: <2023101214-trilogy-wildcard-29cb@gregkh> (raw)
In-Reply-To: <20231011073204.1069793-1-zyytlz.wz@163.com>
On Wed, Oct 11, 2023 at 03:32:04PM +0800, Zheng Wang wrote:
> This is a security bug that has been reported to google.
> It affected all platforms on chrome-os. Please apply this
> patch to 4.14 4.19 5.4 5.10 and 5.15.
>
> [ Upstream commit c677d7ae83141d390d1253abebafa49c962afb52 ]
Did you try to apply this? The file:
> drivers/media/platform/mediatek/jpeg/mtk_jpeg_core.c | 1 +
Is not in the kernels you asked for this patch to be applied to.
How did you test this?
confused,
greg k-h
next prev parent reply other threads:[~2023-10-12 17:23 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 7:32 [RESEND PATCH v2] media: mtk-jpeg: Fix use after free bug due to uncanceled work Zheng Wang
2023-10-12 17:23 ` Greg KH [this message]
2023-10-15 10:32 ` Zheng Hacker
-- strict thread matches above, loose matches on Subject: below --
2023-10-11 3:17 Zheng Wang
2023-10-11 4:51 ` kernel test robot
2023-07-07 9:24 Zheng Wang
2023-07-07 9:24 ` Zheng Wang
2023-07-07 14:11 ` Alexandre Mergnat
2023-07-07 14:11 ` Alexandre Mergnat
2023-07-15 16:08 ` Zheng Hacker
2023-07-15 16:08 ` Zheng Hacker
2023-07-18 3:07 ` Zheng Hacker
2023-07-18 3:07 ` Zheng Hacker
2023-07-19 10:17 ` Alexandre Mergnat
2023-07-19 10:17 ` Alexandre Mergnat
2023-07-20 3:17 ` Zheng Hacker
2023-07-20 3:17 ` Zheng Hacker
2023-07-20 3:40 ` Chen-Yu Tsai
2023-07-20 3:40 ` Chen-Yu Tsai
2023-07-20 7:45 ` AngeloGioacchino Del Regno
2023-07-20 7:45 ` AngeloGioacchino Del Regno
2023-07-25 2:39 ` Zheng Hacker
2023-08-22 18:51 ` Dmitry Osipenko
2023-08-22 18:51 ` Dmitry Osipenko
2023-08-24 8:20 ` Zheng Hacker
2023-08-24 8:20 ` Zheng Hacker
2023-08-28 2:04 ` Dmitry Osipenko
2023-08-28 2:04 ` Dmitry Osipenko
2023-08-31 8:18 ` Zheng Hacker
2023-08-31 8:18 ` Zheng Hacker
2023-09-05 4:24 ` Zheng Hacker
2023-09-05 4:24 ` Zheng Hacker
2023-09-12 9:29 ` Zheng Hacker
2023-09-12 9:29 ` Zheng Hacker
2023-09-19 18:24 ` Dmitry Osipenko
2023-09-19 18:24 ` Dmitry Osipenko
2023-09-19 18:25 ` Dmitry Osipenko
2023-09-19 18:25 ` Dmitry Osipenko
2023-10-08 9:13 ` Zheng Hacker
2023-10-08 9:13 ` Zheng Hacker
2023-10-19 19:56 ` Dmitry Osipenko
2023-10-19 19:56 ` Dmitry Osipenko
2023-10-20 2:51 ` Zheng Hacker
2023-10-20 2:51 ` Zheng Hacker
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=2023101214-trilogy-wildcard-29cb@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=amergnat@baylibre.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=hackerzheng666@gmail.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=patches@lists.linux.dev \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=wenst@chromium.org \
--cc=zyytlz.wz@163.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.