Bug 11100 - sysdeps/unix/sysv/linux/ptrace.c PTRACE_SETOPTIONS inappropriate pointer check
Summary: sysdeps/unix/sysv/linux/ptrace.c PTRACE_SETOPTIONS inappropriate pointer check
Status: RESOLVED WONTFIX
Alias: None
Product: glibc
Classification: Unclassified
Component: libc (show other bugs)
Version: unspecified
: P2 minor
Target Milestone: ---
Assignee: Ulrich Drepper
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-16 22:11 UTC by Chris Head
Modified: 2014-06-30 20:31 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:
fweimer: security-

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Head 2009-12-16 22:11:17 UTC 
In sysdeps/unix/sysv/linux/ptrace.c, on line 102, if __BOUNDED__POINTERS__ is 
true, checks are done that pointers point at appropriate locations. Such a 
check is done on the "data" argument to ptrace() if the "request" argument is 
PTRACE_SETOPTIONS. However, according to ptrace(2) (and, indeed, according to 
the gdb sources and the kernel sources), the PTRACE_SETOPTIONS request accepts 
a bitmask of PTRACE_O_* values as its "data" argument, *not* a pointer.
Comment 1 Ulrich Drepper 2010-04-05 04:29:58 UTC 
__BOUNDED__POINTERS__ is not supported and never really worked.  The code is
only left in place in case there is some future technology coming which can use
that information.
Comment 2 Chris Head 2010-04-05 08:11:59 UTC 
No big deal, it didn't actually impact me—I just saw it and thought I'd point 
out that it looks like it shouldn't be there.