From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Chen Ridong <chenridong@huaweicloud.com>
Cc: ysato@users.sourceforge.jp, dalias@libc.org,
glaubitz@physik.fu-berlin.de, gregkh@linuxfoundation.org,
ricardo@marliere.net, damm@opensource.se, lethal@linux-sh.org,
linux-sh@vger.kernel.org, chenridong@huawei.com,
wangweiyang2@huawei.com
Subject: Re: [PATCH] sh: intc: Fix possible UAF in register_intc_controller
Date: Wed, 13 Nov 2024 09:26:28 +0100 [thread overview]
Message-ID: <CAMuHMdXznLuo7QegG9giQo80HcRmV4MgKh67sWy2WJXd4Pry+Q@mail.gmail.com> (raw)
In-Reply-To: <20241030060813.1307698-1-chenridong@huaweicloud.com>
On Wed, Oct 30, 2024 at 7:17 AM Chen Ridong <chenridong@huaweicloud.com> wrote:
> From: Chen Ridong <chenridong@huawei.com>
>
> When it goes to error, the 'd' is freed, but 'd->list' was not deleted
> from 'intc_list', which may lead to a UAF.
>
> Fixes: 01e9651a21bc ("sh: add INTC out of memory error handling")
> Signed-off-by: Chen Ridong <chenridong@huawei.com>
Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2024-11-13 8:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-30 6:08 [PATCH] sh: intc: Fix possible UAF in register_intc_controller Chen Ridong
2024-11-07 0:57 ` Chen Ridong
2024-11-07 7:35 ` John Paul Adrian Glaubitz
2024-11-07 7:57 ` Chen Ridong
2024-11-13 6:21 ` Chen Ridong
2024-11-13 8:35 ` John Paul Adrian Glaubitz
2024-11-14 3:02 ` Chen Ridong
2024-11-13 8:26 ` Geert Uytterhoeven [this message]
2024-11-25 1:21 ` Chen Ridong
2024-11-25 7:13 ` John Paul Adrian Glaubitz
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=CAMuHMdXznLuo7QegG9giQo80HcRmV4MgKh67sWy2WJXd4Pry+Q@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=chenridong@huawei.com \
--cc=chenridong@huaweicloud.com \
--cc=dalias@libc.org \
--cc=damm@opensource.se \
--cc=glaubitz@physik.fu-berlin.de \
--cc=gregkh@linuxfoundation.org \
--cc=lethal@linux-sh.org \
--cc=linux-sh@vger.kernel.org \
--cc=ricardo@marliere.net \
--cc=wangweiyang2@huawei.com \
--cc=ysato@users.sourceforge.jp \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).