public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <kees@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, David Gow <davidgow@google.com>,
	Ivan Orlov <ivan.orlov0322@gmail.com>,
	Kees Cook <kees@kernel.org>, Luis Chamberlain <mcgrof@kernel.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Petr Mladek <pmladek@suse.com>, Petr Pavlu <petr.pavlu@suse.com>,
	Sami Tolvanen <samitolvanen@google.com>,
	Song Liu <song@kernel.org>,
	Thorsten Blum <thorsten.blum@toblux.com>
Subject: [GIT PULL] hardening fixes for v6.11-rc4
Date: Thu, 15 Aug 2024 11:08:30 -0700	[thread overview]
Message-ID: <202408151107.18E1DC8CE4@keescook> (raw)

Hi Linus,

Please pull these various hardening fixes for v6.11-rc4.

Thanks!

-Kees

The following changes since commit de9c2c66ad8e787abec7c9d7eff4f8c3cdd28aed:

  Linux 6.11-rc2 (2024-08-04 13:50:53 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/hardening-v6.11-rc4

for you to fetch changes up to fb6a421fb6153d97cf3058f9bd550b377b76a490:

  kallsyms: Match symbols exactly with CONFIG_LTO_CLANG (2024-08-15 09:33:35 -0700)

----------------------------------------------------------------
hardening fixes for v6.11-rc4

- gcc-plugins: randstruct: Remove GCC 4.7 or newer requirement
  (Thorsten Blum)

- kallsyms: Clean up interaction with LTO suffixes (Song Liu)

- refcount: Report UAF for refcount_sub_and_test(0) when counter==0
  (Petr Pavlu)

- kunit/overflow: Avoid misallocation of driver name (Ivan Orlov)

----------------------------------------------------------------
Ivan Orlov (1):
      kunit/overflow: Fix UB in overflow_allocation_test

Petr Pavlu (1):
      refcount: Report UAF for refcount_sub_and_test(0) when counter==0

Song Liu (2):
      kallsyms: Do not cleanup .llvm.<hash> suffix before sorting symbols
      kallsyms: Match symbols exactly with CONFIG_LTO_CLANG

Thorsten Blum (1):
      gcc-plugins: randstruct: Remove GCC 4.7 or newer requirement

 drivers/misc/lkdtm/refcount.c                 | 16 ++++++++
 include/linux/refcount.h                      |  4 +-
 kernel/kallsyms.c                             | 55 +++------------------------
 kernel/kallsyms_selftest.c                    | 22 +----------
 lib/overflow_kunit.c                          |  3 +-
 scripts/gcc-plugins/randomize_layout_plugin.c |  4 --
 scripts/kallsyms.c                            | 31 +--------------
 scripts/link-vmlinux.sh                       |  4 --
 8 files changed, 28 insertions(+), 111 deletions(-)

-- 
Kees Cook

             reply	other threads:[~2024-08-15 18:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-15 18:08 Kees Cook [this message]
2024-08-15 19:25 ` [GIT PULL] hardening fixes for v6.11-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=202408151107.18E1DC8CE4@keescook \
    --to=kees@kernel.org \
    --cc=davidgow@google.com \
    --cc=ivan.orlov0322@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=peterz@infradead.org \
    --cc=petr.pavlu@suse.com \
    --cc=pmladek@suse.com \
    --cc=samitolvanen@google.com \
    --cc=song@kernel.org \
    --cc=thorsten.blum@toblux.com \
    --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