From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
"Lorenzo Stoakes (ARM)" <ljs@kernel.org>
Subject: Re: [PATCH 5.15.y] mm/vmalloc: acquire init_mm lock on huge vmap to avoid ptdump UAF
Date: Wed, 21 Oct 2026 22:03:27 -0400 [thread overview]
Message-ID: <2026-10-21-1-daily-reply-0002-vmalloc-ptdump-5-15@kernel.org> (raw)
In-Reply-To: <20261020093017.750359-1-ljs@kernel.org>
> Currently there is a nasty race between ptdump and vmap when attempting to
> map a huge P4D, PUD or PMD entry:
Queued for 5.15, thanks.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-10-22 2:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 12:23 FAILED: patch "[PATCH] mm/vmalloc: acquire init_mm lock on huge vmap to avoid ptdump" failed to apply to 5.15-stable tree gregkh
2026-10-20 9:30 ` [PATCH 5.15.y] mm/vmalloc: acquire init_mm lock on huge vmap to avoid ptdump UAF Lorenzo Stoakes (ARM)
2026-10-22 2:03 ` Sasha Levin [this message]
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=2026-10-21-1-daily-reply-0002-vmalloc-ptdump-5-15@kernel.org \
--to=sashal@kernel.org \
--cc=ljs@kernel.org \
--cc=stable@vger.kernel.org \
/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