linux-kernel - Re: [PATCH] [ipc/sem.c] fix race with concurrent semtimedop() timeouts and IPC

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] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 20 Jul 2011 23:58:36 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Manfred Spraul <manfred@...orfullife.com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Yuriy Yevtukhov <yuriy@...z.com>
Subject: Re: [PATCH] [ipc/sem.c] fix race with concurrent semtimedop()
 timeouts and IPC_RMID

On Thu, 21 Jul 2011 08:42:53 +0200 Manfred Spraul <manfred@...orfullife.com> wrote:

> If a semaphore array is removed and in parallel a sleeping task is woken up
> (signal or timeout, does not matter), then the woken up task does not wait
> until wake_up_sem_queue_do() is completed. This will cause crashes, because
> wake_up_sem_queue_do() will read from a stale pointer.
> 
> The fix is simple: Regardless of anything, always call get_queue_result().
> This function waits until wake_up_sem_queue_do() has finished it's task.
> 
> Andrew, could you please take care of merging the patch?

yup, thanks for this.  It's good to hear from you, and that you've
still got what it takes :)

Do you know how long this bug has been around for?  Somewhere between
2.6.32 and 2.6.36, but that a large interval!
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/