linux-kernel - Re: [PATCH] time/alarmtimer: Add bounds checking for the timer interval and expiration

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.20.1706121740170.1911@nanos>
Date:   Mon, 12 Jun 2017 17:41:30 +0200 (CEST)
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Prarit Bhargava <prarit@...hat.com>
cc:     linux-kernel@...r.kernel.org, John Stultz <john.stultz@...aro.org>,
        Stephen Boyd <sboyd@...eaurora.org>
Subject: Re: [PATCH] time/alarmtimer: Add bounds checking for the timer
 interval and expiration

On Mon, 12 Jun 2017, Prarit Bhargava wrote:

> Running the syzkaller timer_hang_poc.c
> (https://groups.google.com/forum/#!topic/syzkaller/355tWdc8oHY) causes a
> kernel hang by passing in a time that results in the timer being started
> with an expiration that exceeds KTIME_MAX.
> 
> Check for overflow values of expiration (exp) and interval.
> 
> Also cleanup the code.  Set and check the values, and then modify the
> timer.

This is already addressed in

git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git timers/urgent

I just did not come around to send it to Linus last week.

Thanks,

	tglx