diff options
author | Maciej W. Rozycki <macro@imgtec.com> | 2015-10-26 15:48:19 +0000 |
---|---|---|
committer | Al Viro <viro@zeniv.linux.org.uk> | 2015-11-11 02:18:07 -0500 |
commit | b582ef5c53040c5feef4c96a8f9585b6831e2441 (patch) | |
tree | 0dfe5b64ffdbdaea441ee58bab03362e25df810b /fs/pipe.c | |
parent | 102f4d900c9c8f5ed89ae4746d493fe3ebd7ba64 (diff) | |
download | op-kernel-dev-b582ef5c53040c5feef4c96a8f9585b6831e2441.zip op-kernel-dev-b582ef5c53040c5feef4c96a8f9585b6831e2441.tar.gz |
binfmt_elf: Don't clobber passed executable's file header
Do not clobber the buffer space passed from `search_binary_handler' and
originally preloaded by `prepare_binprm' with the executable's file
header by overwriting it with its interpreter's file header. Instead
keep the buffer space intact and directly use the data structure locally
allocated for the interpreter's file header, fixing a bug introduced in
2.1.14 with loadable module support (linux-mips.org commit beb11695
[Import of Linux/MIPS 2.1.14], predating kernel.org repo's history).
Adjust the amount of data read from the interpreter's file accordingly.
This was not an issue before loadable module support, because back then
`load_elf_binary' was executed only once for a given ELF executable,
whether the function succeeded or failed.
With loadable module support supported and enabled, upon a failure of
`load_elf_binary' -- which may for example be caused by architecture
code rejecting an executable due to a missing hardware feature requested
in the file header -- a module load is attempted and then the function
reexecuted by `search_binary_handler'. With the executable's file
header replaced with its interpreter's file header the executable can
then be erroneously accepted in this subsequent attempt.
Cc: stable@vger.kernel.org # all the way back
Signed-off-by: Maciej W. Rozycki <macro@imgtec.com>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'fs/pipe.c')
0 files changed, 0 insertions, 0 deletions