From: Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>
To: Vitaliy Shevtsov <v.shevtsov@maxima.ru>
Cc: Jason Gunthorpe <jgg@ziepe.ca>, Leon Romanovsky <leon@kernel.org>,
Doug Ledford <dledford@redhat.com>,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
lvc-project@linuxtesting.org
Subject: Re: [PATCH] IB/hfi1: fix buffer underflow in fault injection code
Date: Wed, 15 Jan 2025 12:55:04 -0500 [thread overview]
Message-ID: <4e7675a0-0dc0-4da3-b8ae-2462a5b112d1@cornelisnetworks.com> (raw)
In-Reply-To: <20241227230940.20894-1-v.shevtsov@maxima.ru>
On 12/27/24 6:09 PM, Vitaliy Shevtsov wrote:
> [Why]
> The fault injection code may have a buffer underflow, which may cause
> memory corruption by writing a newline character before the base address of
> the array. This can happen if the fault->opcodes bitmap is empty.
>
> Since a file in debugfs is created with an empty bitmap, it is possible to
> read the file before any set bits are written to it.
>
> [How]
> Fix this by checking that the size variable is greater than zero, otherwise
> return zero as the number of bytes read.
>
> Found by Linux Verification Center (linuxtesting.org) with Svace.
>
> Fixes: a74d5307caba ("IB/hfi1: Rework fault injection machinery")
> Signed-off-by: Vitaliy Shevtsov <v.shevtsov@maxima.ru>
> ---
> drivers/infiniband/hw/hfi1/fault.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/infiniband/hw/hfi1/fault.c b/drivers/infiniband/hw/hfi1/fault.c
> index ec9ee59fcf0c..2d87f9c8b89d 100644
> --- a/drivers/infiniband/hw/hfi1/fault.c
> +++ b/drivers/infiniband/hw/hfi1/fault.c
> @@ -190,7 +190,8 @@ static ssize_t fault_opcodes_read(struct file *file, char __user *buf,
> bit = find_next_bit(fault->opcodes, bitsize, zero);
> }
> debugfs_file_put(file->f_path.dentry);
> - data[size - 1] = '\n';
> + if (size)
> + data[size - 1] = '\n';
> data[size] = '\0';
> ret = simple_read_from_buffer(buf, len, pos, data, size);
> free_data:
I don't think size can ever be 0. No reason to change this I don't think.
-Denny
next prev parent reply other threads:[~2025-01-15 17:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-27 23:09 Vitaliy Shevtsov
2025-01-15 17:55 ` Dennis Dalessandro [this message]
2025-01-15 19:14 ` [lvc-project] " Fedor Pchelkin
2025-01-16 4:16 ` Dennis Dalessandro
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=4e7675a0-0dc0-4da3-b8ae-2462a5b112d1@cornelisnetworks.com \
--to=dennis.dalessandro@cornelisnetworks.com \
--cc=dledford@redhat.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=v.shevtsov@maxima.ru \
/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
all inboxes | Powered by JetHome®