From: Corey Minyard <minyard@acm.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: andrew.manley@sealingtech.com,
openipmi-developer@lists.sourceforge.net,
linux-kernel@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH] ipmi: fix oob access due to uninit smi_msg type
Date: Thu, 25 Nov 2021 08:21:40 -0600 [thread overview]
Message-ID: <20211125142140.GV15676@minyard.net> (raw)
In-Reply-To: <20211124210323.1950976-1-kuba@kernel.org>
On Wed, Nov 24, 2021 at 01:03:23PM -0800, Jakub Kicinski wrote:
> We're hitting OOB accesses in handle_ipmb_direct_rcv_rsp() (memcpy of
> size -1) after user space generates a message. Looks like the message
> is incorrectly assumed to be of the new IPMB type, because type is never
> set and message is allocated with kmalloc() not kzalloc().
>
> Fixes: 059747c245f0 ("ipmi: Add support for IPMB direct messages")
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
This is correct, and in my queue. Thanks for the fix.
-corey
> ---
> Would it be possible to get something like this to Linus ASAP?
> It's flipping over all my test boxes.
> ---
> drivers/char/ipmi/ipmi_msghandler.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/char/ipmi/ipmi_msghandler.c b/drivers/char/ipmi/ipmi_msghandler.c
> index deed355422f4..f0b18c25cbb1 100644
> --- a/drivers/char/ipmi/ipmi_msghandler.c
> +++ b/drivers/char/ipmi/ipmi_msghandler.c
> @@ -5031,6 +5031,7 @@ struct ipmi_smi_msg *ipmi_alloc_smi_msg(void)
> if (rv) {
> rv->done = free_smi_msg;
> rv->user_data = NULL;
> + rv->type = IPMI_SMI_MSG_TYPE_NORMAL;
> atomic_inc(&smi_msg_inuse_count);
> }
> return rv;
> --
> 2.31.1
>
next prev parent reply other threads:[~2021-11-25 14:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-24 21:03 [PATCH] ipmi: fix oob access due to uninit smi_msg type Jakub Kicinski
2021-11-25 14:21 ` Corey Minyard [this message]
2021-11-25 15:05 ` Jakub Kicinski
2021-11-26 3:28 ` Corey Minyard
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=20211125142140.GV15676@minyard.net \
--to=minyard@acm.org \
--cc=andrew.manley@sealingtech.com \
--cc=kernel-team@fb.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openipmi-developer@lists.sourceforge.net \
/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.