From: Bin Lan <lanbincn@139.com>
To: gregkh@linuxfoundation.org, sashal@kernel.org, stable@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, steffen.klassert@secunet.com,
daniel.m.jordan@oracle.com, linux-crypto@vger.kernel.org,
Bin Lan <lanbincn@139.com>
Subject: [PATCH 5.15.y 0/2] backport to fix a race condition/UAF in the
Date: Tue, 28 Apr 2026 13:07:57 +0800 [thread overview]
Message-ID: <20260428050800.10488-1-lanbincn@139.com> (raw)
This series backports the padata use-after-free fix and its follow-up
cleanup to the 5.15.y stable branch. There is a race condition in
padata_reorder() dating back to the initial padata commit.
Backport notes for 5.15.y:
- The upstream fix (commit 71203f68c774) was written against mainline
which uses the 2-argument cpumask_next_wrap(cpu, mask) API introduced
by dc5bb9b769c9 ("cpumask: deprecate cpumask_next_wrap()"). Since
6.1.y still has the original 4-argument API, the call in
padata_reorder() is adapted to:
cpumask_next_wrap(cpu, pd->cpumask.pcpu, -1, false)
This is functionally equivalent.
- The context in padata_find_next() differs from mainline due to
f954a2d37637 ("padata: switch padata_find_next() to using
cpumask_next_wrap()") not being present in 6.1.y. The conflict was
resolved.
After applying this series, kernel/padata.c matches the upstream file at
commit 71203f68c774 with a few differences. None of these differences
affect the fix, the core changes to padata_find_next(), padata_reorder(),
and padata_do_serial() are identical.
Testing:
- Built and booted on x86_64 (4 CPUs, 5.15.202-yocto-standard)
- All 4 test cases passed:
* Basic parallel->serial reorder (64 jobs)
* Out-of-order parallel completion reorder (64 jobs)
* Concurrent jobs + padata_replace race (64 jobs)
* Stress test (10 iterations x 64 jobs, random delays)
- No KASAN/BUG/WARNING/UAF detected in dmesg
Bin Lan
Herbert Xu (2):
padata: Fix pd UAF once and for all
padata: Remove comment for reorder_work
include/linux/padata.h | 4 --
kernel/padata.c | 136 +++++++++++------------------------------
2 files changed, 37 insertions(+), 103 deletions(-)
--
2.43.0
next reply other threads:[~2026-04-28 5:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 5:07 Bin Lan [this message]
2026-04-28 5:07 ` [PATCH 5.15.y 1/2] padata: Fix pd UAF once and for all Bin Lan
2026-04-28 5:07 ` [PATCH 5.15.y 2/2] padata: Remove comment for reorder_work Bin Lan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260428050800.10488-1-lanbincn@139.com \
--to=lanbincn@139.com \
--cc=daniel.m.jordan@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=steffen.klassert@secunet.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox