From 533deafbdf189f5fbb280c28562dd43ace2f4b0f Mon Sep 17 00:00:00 2001 From: Sergey Bugaev Date: Wed, 19 Apr 2023 19:02:03 +0300 Subject: Use O_CLOEXEC in more places (BZ #15722) When opening a temporary file without O_CLOEXEC we risk leaking the file descriptor if another thread calls (fork and then) exec while we have the fd open. Fix this by consistently passing O_CLOEXEC everywhere where we open a file for internal use (and not to return it to the user, in which case the API defines whether or not the close-on-exec flag shall be set on the returned fd). Reviewed-by: Adhemerval Zanella Signed-off-by: Sergey Bugaev Message-Id: <20230419160207.65988-4-bugaevc@gmail.com> --- login/utmp_file.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'login') diff --git a/login/utmp_file.c b/login/utmp_file.c index 5349459581..1ef0782139 100644 --- a/login/utmp_file.c +++ b/login/utmp_file.c @@ -463,7 +463,7 @@ __libc_updwtmp (const char *file, const struct utmp *utmp) int fd; /* Open WTMP file. */ - fd = __open_nocancel (file, O_WRONLY | O_LARGEFILE); + fd = __open_nocancel (file, O_WRONLY | O_LARGEFILE | O_CLOEXEC); if (fd < 0) return -1; -- cgit 1.4.1