From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] syscalls/fork14: Fix Buffer overflow
Date: Thu, 11 Jun 2020 07:33:56 -0400 (EDT) [thread overview]
Message-ID: <1118360748.15618585.1591875236530.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20200609071611.9467-1-vikas.kumar2@arm.com>
----- Original Message -----
> This change basically avoids the buffer overflow by keeping the check count
> to allocation limit
> The problem occurs when there is no failure and i == EXTENT, so
> pointer_vec[EXTENT] goes beyond the allocated buffer.
I changed the patch to use a new variable, that reflects number of used
fields, and pushed.
Thanks,
Jan
prev parent reply other threads:[~2020-06-11 11:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 7:16 [LTP] [PATCH] syscalls/fork14: Fix Buffer overflow Vikas Kumar
2020-06-11 11:33 ` Jan Stancek [this message]
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=1118360748.15618585.1591875236530.JavaMail.zimbra@redhat.com \
--to=jstancek@redhat.com \
--cc=ltp@lists.linux.it \
/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