public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	"Borislav Petkov (AMD)" <bp@alien8.de>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Gustavo A. R. Silva" <gustavoars@kernel.org>,
	Kees Cook <keescook@chromium.org>,
	Matthias Kaehlcke <mka@chromium.org>,
	Mirsad Todorovac <mirsad.todorovac@alu.unizg.hr>
Subject: [GIT PULL] hardening updates for v6.5-rc1-fixes
Date: Fri, 7 Jul 2023 11:12:28 -0700	[thread overview]
Message-ID: <202307071111.63B0BFB323@keescook> (raw)

Hi Linus,

Please pull these handful of kernel hardening fixes for v6.5-rc1.

Thanks!

-Kees

The following changes since commit acf15e07eb06507c69f92394c36052677029b0a8:

  netfilter: ipset: Replace strlcpy with strscpy (2023-06-20 13:35:37 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/hardening-v6.5-rc1-fixes

for you to fetch changes up to 01f23c5f1526f5b6ff744887aa511b9e69d4401b:

  usb: ch9: Replace bmSublinkSpeedAttr 1-element array with flexible array (2023-07-05 14:11:30 -0700)

----------------------------------------------------------------
hardening fixes for v6.5-rc1

- Check for NULL bdev in LoadPin (Matthias Kaehlcke)

- Revert unwanted KUnit FORTIFY build default

- Fix 1-element array causing boot warnings with xhci-hub

----------------------------------------------------------------
Kees Cook (2):
      Revert "fortify: Allow KUnit test to build without FORTIFY"
      usb: ch9: Replace bmSublinkSpeedAttr 1-element array with flexible array

Matthias Kaehlcke (1):
      dm: verity-loadpin: Add NULL pointer check for 'bdev' parameter

 drivers/md/dm-verity-loadpin.c |  3 +++
 include/uapi/linux/usb/ch9.h   |  6 +++++-
 lib/Kconfig.debug              |  2 +-
 lib/fortify_kunit.c            | 14 --------------
 4 files changed, 9 insertions(+), 16 deletions(-)

-- 
Kees Cook

             reply	other threads:[~2023-07-07 18:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-07 18:12 Kees Cook [this message]
2023-07-08 19:18 ` [GIT PULL] hardening updates for v6.5-rc1-fixes 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=202307071111.63B0BFB323@keescook \
    --to=keescook@chromium.org \
    --cc=bp@alien8.de \
    --cc=geert@linux-m68k.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=gustavoars@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mirsad.todorovac@alu.unizg.hr \
    --cc=mka@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