From: Siddhesh Poyarekar <siddhesh@sourceware.org>
To: libc-stable@sourceware.org
Subject: [committed 2.34 0/6] Fixes for CVE-2021-3998 and CVE-2021-3999
Date: Mon, 24 Jan 2022 12:20:36 +0530 [thread overview]
Message-ID: <20220124065042.3497514-1-siddhesh@sourceware.org> (raw)
Backported to 2.34 branch.
Siddhesh Poyarekar (6):
support: Add helpers to create paths longer than PATH_MAX
stdlib: Sort tests in Makefile
stdlib: Fix formatting of tests list in Makefile
realpath: Set errno to ENAMETOOLONG for result larger than PATH_MAX
[BZ #28770]
tst-realpath-toolong: Fix hurd build
getcwd: Set errno to ERANGE for size == 1 (CVE-2021-3999)
NEWS | 10 +
stdlib/Makefile | 102 ++++++--
stdlib/canonicalize.c | 12 +-
stdlib/tst-realpath-toolong.c | 53 ++++
support/temp_file.c | 161 +++++++++++-
support/temp_file.h | 9 +
sysdeps/posix/getcwd.c | 7 +
sysdeps/unix/sysv/linux/Makefile | 7 +-
.../unix/sysv/linux/tst-getcwd-smallbuff.c | 241 ++++++++++++++++++
9 files changed, 565 insertions(+), 37 deletions(-)
create mode 100644 stdlib/tst-realpath-toolong.c
create mode 100644 sysdeps/unix/sysv/linux/tst-getcwd-smallbuff.c
--
2.34.1
next reply other threads:[~2022-01-24 6:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 6:50 Siddhesh Poyarekar [this message]
2022-01-24 6:50 ` [committed 2.34 1/6] support: Add helpers to create paths longer than PATH_MAX Siddhesh Poyarekar
2022-01-24 6:50 ` [committed 2.34 2/6] stdlib: Sort tests in Makefile Siddhesh Poyarekar
2022-01-24 6:50 ` [committed 2.34 3/6] stdlib: Fix formatting of tests list " Siddhesh Poyarekar
2022-01-24 6:50 ` [committed 2.34 4/6] realpath: Set errno to ENAMETOOLONG for result larger than PATH_MAX [BZ #28770] Siddhesh Poyarekar
2022-01-24 6:50 ` [committed 2.34 5/6] tst-realpath-toolong: Fix hurd build Siddhesh Poyarekar
2022-01-24 6:50 ` [committed 2.34 6/6] getcwd: Set errno to ERANGE for size == 1 (CVE-2021-3999) Siddhesh Poyarekar
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=20220124065042.3497514-1-siddhesh@sourceware.org \
--to=siddhesh@sourceware.org \
--cc=libc-stable@sourceware.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).