mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Douglas Anderson <dianders@chromium.org>,
	Kees Cook <keescook@chromium.org>,
	Masahiro Yamada <masahiroy@kernel.org>,
	Nathan Chancellor <nathan@kernel.org>,
	Stephen Boyd <swboyd@chromium.org>
Subject: [GIT PULL] hardening fixes for v6.10-rc1
Date: Thu, 23 May 2024 16:37:56 -0700	[thread overview]
Message-ID: <202405231637.664DFA26FA@keescook> (raw)

Hi Linus,

Please pull these hardening fixes for v6.10-rc1-fixes.

Thanks!

-Kees

The following changes since commit 6d305cbef1aa01b9714e01e35f3d5c28544cf04d:

  uapi: stddef.h: Provide UAPI macros for __counted_by_{le, be} (2024-05-08 00:42:25 -0700)

are available in the Git repository at:

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

for you to fetch changes up to ae1a863bcdbd6ea2abc93519a82ab5d715d5dcbc:

  kunit/fortify: Fix memcmp() test to be amplitude agnostic (2024-05-18 13:46:10 -0700)

----------------------------------------------------------------
hardening fixes for v6.10-rc1

- loadpin: Prevent SECURITY_LOADPIN_ENFORCE=y without module decompression
  (Stephen Boyd)

- ubsan: Restore dependency on ARCH_HAS_UBSAN

- kunit/fortify: Fix memcmp() test to be amplitude agnostic

----------------------------------------------------------------
Kees Cook (2):
      ubsan: Restore dependency on ARCH_HAS_UBSAN
      kunit/fortify: Fix memcmp() test to be amplitude agnostic

Stephen Boyd (1):
      loadpin: Prevent SECURITY_LOADPIN_ENFORCE=y without module decompression

 lib/Kconfig.ubsan        | 1 +
 lib/fortify_kunit.c      | 2 +-
 security/loadpin/Kconfig | 3 +++
 3 files changed, 5 insertions(+), 1 deletion(-)

-- 
Kees Cook

             reply	other threads:[~2024-05-23 23:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-23 23:37 Kees Cook [this message]
2024-05-24 16:45 ` 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=202405231637.664DFA26FA@keescook \
    --to=keescook@chromium.org \
    --cc=dianders@chromium.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=nathan@kernel.org \
    --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

all inboxes | Powered by JetHome®