https://bugs.kde.org/show_bug.cgi?id=450437
Bug ID: 450437
Summary: Warn for execve syscall with argv or argv[0] being
NULL.
Product: valgrind
Version: 3.18.1
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: jsew...@acm.org
Reporter: m...@klomp.org
CC: aria...@dereferenced.org
Target Milestone: ---
Created attachment 146855
--> https://bugs.kde.org/attachment.cgi?id=146855&action=edit
Warn for execve syscall with argv or argv[0] being NULL
For execve valgrind would silently fail when argv was NULL or
unadressable. Make sure that this produces a warning under memcheck.
The linux kernel accepts argv[0] being NULL, but most other kernels
don't since posix says it should be non-NULL and it causes argc to
be zero which is unexpected and might cause security issues.
This adjusts some testcases so they don't rely on execve succeeding
when argv is NULL and expect warnings about argv or argv[0] being
NULL or unaddressable.
See also https://lwn.net/Articles/882799/
--
You are receiving this mail because:
You are watching all bug changes.
