timers/timer_create: Add test for CVE-2017-18344
PATCH 1/1 timers/timer_create: Add test for CVE-2017-18344
In kernels prior to 4.14.8 (missing commit cef31d9af908) the sigevent.sigev_notify field is not properly checked when creating a timer using timer_create(2). This can be used to read arbitrary kernel memory.
Signed-off-by Christian Amann <[email protected]>
--- runtest/timers | 1 + testcases/kernel/timers/timer_create/.gitignore | 1 + .../kernel/timers/timer_create/timer_create05.c | 67 ++++++++++++++++++++++ 3 files changed, 69 insertions(+) create mode 100644 testcases/kernel/timers/timer_create/timer_create05.c
runtest/timers +1 -0
@@ -1,6 +1,7 @@ #DESCRIPTION:Posix Timer Tests timer_create02 timer_create02 timer_create04 timer_create04 +timer_create05 timer_create05 timer_delete02 timer_delete02 timer_delete03 timer_delete03 timer_settime02 timer_settime02
testcases/kernel/timers/timer_create/.gitignore +1 -0
@@ -1,2 +1,3 @@ /timer_create02 /timer_create04 +/timer_create05
testcases/kernel/timers/timer_create/timer_create05.c new file +67 -0
67 lines not on this page · raw message
Signature · 1 line
2.16.4
PATCH 1/1 timers/timer_create: Add test for CVE-2017-18344
Hi!
Quoted 4 lines
In kernels prior to 4.14.8 (missing commit
cef31d9af908) the sigevent.sigev_notify field is not properly checked when creating a timer usingtimer_create(2). This can be used to read arbitrary kernel memory.
This is fine but I would like to move the timers into the syscalls directory before we start to add new testcases. Should I do the move or will you send a patch?
Signature · 2 lines
Cyril Hrubis [email protected]