1 .\" Copyright (c) 2006, 2014, Michael Kerrisk
3 .\" %%%LICENSE_START(VERBATIM)
4 .\" Permission is granted to make and distribute verbatim copies of this
5 .\" manual provided the copyright notice and this permission notice are
6 .\" preserved on all copies.
8 .\" Permission is granted to copy and distribute modified versions of this
9 .\" manual under the conditions for verbatim copying, provided that the
10 .\" entire resulting derived work is distributed under the terms of a
11 .\" permission notice identical to this one.
13 .\" Since the Linux kernel and libraries are constantly changing, this
14 .\" manual page may be incorrect or out-of-date. The author(s) assume no
15 .\" responsibility for errors or omissions, or for damages resulting from
16 .\" the use of the information contained herein. The author(s) may not
17 .\" have taken the same level of care in the production of this manual,
18 .\" which is licensed free of charge, as they might when working
21 .\" Formatted or processed versions of this manual, if unaccompanied by
22 .\" the source, must acknowledge the copyright and authors of this work.
25 .TH FEXECVE 3 2015-07-23 "Linux" "Linux Programmer's Manual"
27 fexecve \- execute program specified via file descriptor
30 .B #include <unistd.h>
32 .BI "int fexecve(int " fd ", char *const " argv "[], char *const " envp []);
36 Feature Test Macro Requirements for glibc (see
37 .BR feature_test_macros (7)):
46 _XOPEN_SOURCE\ >=\ 700 || _POSIX_C_SOURCE\ >=\ 200809L
55 performs the same task as
57 with the difference that the file to be executed
58 is specified via a file descriptor,
60 rather than via a pathname.
63 must be opened read-only,
64 and the caller must have permission to execute the file that it refers to.
65 .\" POSIX.1-2008 specifies the O_EXEC flag for open as an alternative,
66 .\" but Linux doesn't support this flag yet.
71 On error, the function does return, with a result value of \-1, and
77 with the following additions:
81 is not a valid file descriptor, or
90 filesystem could not be accessed.
93 is implemented since glibc 2.3.2.
95 For an explanation of the terms used in this section, see
101 Interface Attribute Value
104 T} Thread safety MT-Safe
109 This function is not specified in POSIX.1-2001,
110 and is not widely available on other systems.
111 It is specified in POSIX.1-2008.
115 is implemented using the
119 needs to be mounted and available at the time of the call.
121 .\" With the addition of the execveat(2), fexecve() can be implemented
122 .\" even where /proc is unavailable. Review future glibc releases to
123 .\" see if the implementation is changed to use execveat(2).
127 is to allow the caller to verify (checksum) the contents of
128 an executable before executing it.
129 Simply opening the file, checksumming the contents, and then doing an
131 would not suffice, since, between the two steps, the filename,
132 or a directory prefix of the pathname, could have been exchanged
133 (by, for example, modifying the target of a symbolic link).
135 does not mitigate the problem that the
137 of a file could be changed between the checksumming and the call to
139 for that, the solution is to ensure that the permissions on the file
140 prevent it from being modified by malicious users.
142 The natural idiom when using
144 is to set the close-on-exec flag on
146 so that the file descriptor does not leak through to the program
148 This approach is natural for two reasons.
149 First, it prevents file descriptors being consumed unnecessarily.
150 (The executed program normally has no need of a file descriptor
151 that refers to the program itself.)
155 employing the close-on-exec flag prevents the file descriptor exhaustion
156 that would result from the fact that each step in the recursion would
157 cause one more file descriptor to be passed to the new program.
162 refers to a script (i.e., it is an executable text file that names
163 a script interpreter with a first line that begins with the characters
165 and the close-on-exec flag has been set for
171 This error occurs because,
172 by the time the script interpreter is executed,
174 has already been closed because of the close-on-exec flag.
175 Thus, the close-on-exec flag can't be set on
177 if it refers to a script, leading to the problems described in NOTES.