From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Brian Norris <briannorris@chromium.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Guenter Roeck <groeck@chromium.org>,
Jack Rosenthal <jrosenth@chromium.org>,
Julius Werner <jwerner@chromium.org>,
Kees Cook <keescook@chromium.org>,
Paul Menzel <pmenzel@molgen.mpg.de>,
Peter Zijlstra <peterz@infradead.org>,
Sami Tolvanen <samitolvanen@google.com>,
Stephen Boyd <swboyd@chromium.org>
Subject: [GIT PULL] kernel hardening fixes for v6.2-rc4
Date: Fri, 13 Jan 2023 15:27:05 -0800 [thread overview]
Message-ID: <202301131526.28719A40@keescook> (raw)
Hi Linus,
Please pull these two kernel hardening fixes for v6.2-rc4.
Thanks!
-Kees
The following changes since commit 88603b6dc419445847923fcb7fe5080067a30f98:
Linux 6.2-rc2 (2023-01-01 13:53:16 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/hardening-v6.2-rc4
for you to fetch changes up to 42633ed852deadc14d44660ad71e2f6640239120:
kbuild: Fix CFI hash randomization with KASAN (2023-01-13 15:22:03 -0800)
----------------------------------------------------------------
kernel hardening fixes for v6.2-rc4
- Fix CFI hash randomization with KASAN (Sami Tolvanen)
- Check size of coreboot table entry and use flex-array
----------------------------------------------------------------
Kees Cook (1):
firmware: coreboot: Check size of table entry and use flex-array
Sami Tolvanen (1):
kbuild: Fix CFI hash randomization with KASAN
drivers/firmware/google/coreboot_table.c | 9 +++++++--
drivers/firmware/google/coreboot_table.h | 1 +
init/Makefile | 1 +
scripts/Makefile.vmlinux | 1 +
4 files changed, 10 insertions(+), 2 deletions(-)
--
Kees Cook
next reply other threads:[~2023-01-13 23:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 23:27 Kees Cook [this message]
2023-01-14 16:21 ` [GIT PULL] kernel hardening fixes for v6.2-rc4 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=202301131526.28719A40@keescook \
--to=keescook@chromium.org \
--cc=briannorris@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=groeck@chromium.org \
--cc=jrosenth@chromium.org \
--cc=jwerner@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=pmenzel@molgen.mpg.de \
--cc=samitolvanen@google.com \
--cc=swboyd@chromium.org \
--cc=torvalds@linux-foundation.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