Thread (8 messages) 8 messages, 5 authors, 1d ago

Re: [PATCH v2 1/2] signal: avoid shared siginfo namespace rewrites

From: Andrew Morton <akpm@linux-foundation.org>
Date: 2026-06-28 19:11:20
Also in: lkml, stable

On Mon, 22 Jun 2026 20:25:08 +0000 Bradley Morgan [off-list ref] wrote:
send_signal_locked() rewrites sender ids for the target namespace.
Group sends reuse the same siginfo, so one recipient can affect the
next.

Copy the siginfo before changing it.
Thanks, I'll queue this for 7.3-rc1.  I don't see a need to fast-track
it into mainline, as 7a0cf094944e is from 2019.

Can someone please send along a paragraph which describes the
userspace-visible effects of the bug?  I think this is important when
proposing a backportable fix.  Important for all fixes, really.

I understand that I'm to take no action with "[PATCH v2 2/2] signal:
make send_signal_locked() take const siginfo".

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help