From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Kees Cook <keescook@chromium.org>,
Matthew Wilcox <willy@infradead.org>,
Sami Tolvanen <samitolvanen@google.com>,
Uladzislau Rezki <urezki@gmail.com>,
Zorro Lang <zlang@redhat.com>,
Nathan Chancellor <nathan@kernel.org>
Subject: [GIT PULL] hardening fixes for v5.19-rc3
Date: Wed, 15 Jun 2022 14:07:05 -0700 [thread overview]
Message-ID: <202206151405.D8EDB70EA@keescook> (raw)
Hi Linus,
Please pull these kernel hardening fixes for v5.19-rc3.
Thanks!
-Kees
The following changes since commit b13baccc3850ca8b8cccbf8ed9912dbaa0fdf7f3:
Linux 5.19-rc2 (2022-06-12 16:11:37 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/hardening-v5.19-rc3
for you to fetch changes up to 1dfbe9fcda4afc957f0e371e207ae3cb7e8f3b0e:
usercopy: Make usercopy resilient against ridiculously large copies (2022-06-13 09:54:52 -0700)
----------------------------------------------------------------
hardening fixes for v5.19-rc3
- Correctly handle vm_map areas in hardened usercopy (Matthew Wilcox)
- Adjust CFI RCU usage to avoid boot splats with cpuidle (Sami Tolvanen)
----------------------------------------------------------------
Matthew Wilcox (Oracle) (3):
usercopy: Handle vm_map_ram() areas
usercopy: Cast pointer to an integer once
usercopy: Make usercopy resilient against ridiculously large copies
Sami Tolvanen (1):
cfi: Fix __cfi_slowpath_diag RCU usage with cpuidle
include/linux/vmalloc.h | 1 +
kernel/cfi.c | 22 ++++++++++++++++------
mm/usercopy.c | 26 ++++++++++++--------------
mm/vmalloc.c | 2 +-
4 files changed, 30 insertions(+), 21 deletions(-)
--
Kees Cook
next reply other threads:[~2022-06-15 21:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 21:07 Kees Cook [this message]
2022-06-15 21:28 ` pr-tracker-bot
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=202206151405.D8EDB70EA@keescook \
--to=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=samitolvanen@google.com \
--cc=torvalds@linux-foundation.org \
--cc=urezki@gmail.com \
--cc=willy@infradead.org \
--cc=zlang@redhat.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
all inboxes | Powered by JetHome®