From: Siddhesh Poyarekar <siddhesh@sourceware.org>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
Andreas Schwab <schwab@linux-m68k.org>
Cc: fweimer@redhat.com, Qualys Security Advisory <qsa@qualys.com>,
Siddhesh Poyarekar via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH 3/3] getcwd: Set errno to ERANGE for size == 1 (CVE-2021-3999)
Date: Tue, 18 Jan 2022 20:14:49 +0530 [thread overview]
Message-ID: <956fbbf8-7acd-8411-192d-49e48019aaa5@sourceware.org> (raw)
In-Reply-To: <57e3ccd2-92e8-dad8-0d1f-e4bdaa10d767@linaro.org>
On 18/01/2022 19:29, Adhemerval Zanella via Libc-alpha wrote:
>
> Shouldn't we fix it on posix generic implementation then?
>
I added the shortcircuit in the generic as well as linux
implementations. Should I only restrict it to the posix one?
Technically the posix implementation is the only one that writes beyond
buffer bounds, but the linux target is the only one that has the
reproducer due to the linux-specific features used to get the
underflow+overflow going.
Thanks,
Siddhesh
next prev parent reply other threads:[~2022-01-18 14:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 9:07 [PATCH 0/3] Fixes for CVE-2021-3998 and CVE-2021-3999 Siddhesh Poyarekar
2022-01-18 9:07 ` [PATCH 1/3] support: Add helpers to create paths longer than PATH_MAX Siddhesh Poyarekar
2022-01-18 19:42 ` Adhemerval Zanella
2022-01-19 1:33 ` Siddhesh Poyarekar
2022-01-18 9:07 ` [PATCH 2/3] realpath: Set errno to ENAMETOOLONG for result larger than PATH_MAX [BZ #28770] Siddhesh Poyarekar
2022-01-18 19:43 ` Adhemerval Zanella
2022-01-18 9:07 ` [PATCH 3/3] getcwd: Set errno to ERANGE for size == 1 (CVE-2021-3999) Siddhesh Poyarekar
2022-01-18 11:52 ` Andreas Schwab
2022-01-18 13:10 ` Siddhesh Poyarekar
2022-01-18 13:13 ` Andreas Schwab
2022-01-18 13:16 ` Siddhesh Poyarekar
2022-01-18 13:30 ` Andreas Schwab
2022-01-18 13:33 ` Siddhesh Poyarekar
2022-01-18 13:41 ` Andreas Schwab
2022-01-18 13:45 ` Siddhesh Poyarekar
2022-01-18 13:56 ` Siddhesh Poyarekar
2022-01-18 13:57 ` Andreas Schwab
2022-01-18 14:40 ` Siddhesh Poyarekar
2022-01-18 13:59 ` Adhemerval Zanella
2022-01-18 14:44 ` Siddhesh Poyarekar [this message]
2022-01-18 16:30 ` Adhemerval Zanella
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=956fbbf8-7acd-8411-192d-49e48019aaa5@sourceware.org \
--to=siddhesh@sourceware.org \
--cc=adhemerval.zanella@linaro.org \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=qsa@qualys.com \
--cc=schwab@linux-m68k.org \
/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).