linux-kernel - Re: [PATCH v2 0/2] seccomp: Fix a race with WAIT_KILLABLE

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: <175382125844.1703528.15225839014415526576.b4-ty@kernel.org>
Date: Tue, 29 Jul 2025 13:34:21 -0700
From: Kees Cook <kees@...nel.org>
To: Andy Lutomirski <luto@...capital.net>,
	Will Drewry <wad@...omium.org>,
	Sargun Dhillon <sargun@...gun.me>,
	Shuah Khan <shuah@...nel.org>,
	Johannes Nixdorf <johannes@...dorf.dev>
Cc: Kees Cook <kees@...nel.org>,
	linux-kernel@...r.kernel.org,
	Ali Polatel <alip@...sswob.org>,
	linux-kselftest@...r.kernel.org,
	bpf@...r.kernel.org
Subject: Re: [PATCH v2 0/2] seccomp: Fix a race with WAIT_KILLABLE_RECV if the tracer replies too fast

On Fri, 25 Jul 2025 18:31:17 +0200, Johannes Nixdorf wrote:
> If WAIT_KILLABLE_RECV was specified, and an event is received, the
> tracee's syscall is not supposed to be interruptible. This was not properly
> ensured if the reply was sent too fast, and an interrupting signal was
> received before the reply was processed on the tracee side.
> 
> This series fixes the bug and adds a test case for it to the selftests.
> 
> [...]

With minor edits, applied to for-next/seccomp, thanks!

[1/2] seccomp: Fix a race with WAIT_KILLABLE_RECV if the tracer replies too fast
      https://git.kernel.org/kees/c/cce436aafc2a
[2/2] selftests/seccomp: Add a test for the WAIT_KILLABLE_RECV fast reply race
      https://git.kernel.org/kees/c/b0c9bfbab925

Take care,

-- 
Kees Cook