From: Kees Cook <kees@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
Hans de Goede <hansg@kernel.org>, Kees Cook <kees@kernel.org>,
kernel test robot <lkp@intel.com>, Marco Elver <elver@google.com>,
Nathan Chancellor <nathan@kernel.org>,
syzbot+5245cb609175fb6e8122@syzkaller.appspotmail.com,
zepta <z3ptaa@gmail.com>
Subject: [GIT PULL] hardening fixes for v6.17-rc1
Date: Tue, 29 Jul 2025 17:29:41 -0700 [thread overview]
Message-ID: <202507291728.51BAA26@keescook> (raw)
Hi Linus,
Please pull these hardening fixes for v6.17-rc1. Notably, this contains
the fix for for the GCC __init mess I created with the kstack_erase
annotations.
Thanks!
-Kees
The following changes since commit 32e42ab9fc88a884435c27527a433f61c4d2b61b:
sched/task_stack: Add missing const qualifier to end_of_stack() (2025-07-26 14:28:35 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/hardening-v6.17-rc1-fix1
for you to fetch changes up to f627b51aaa041cba715b59026cf2d9cb1476c7ed:
compiler_types: Provide __no_kstack_erase to disable coverage only on Clang (2025-07-29 17:19:35 -0700)
----------------------------------------------------------------
hardening fixes for v6.17-rc1
- staging: media: atomisp: Fix stack buffer overflow in gmin_get_var_int()
I was asked to carry this fix, so here it is. :)
- fortify: Fix incorrect reporting of read buffer size
- kstack_erase: Fix missed export of renamed KSTACK_ERASE_CFLAGS
- compiler_types: Provide __no_kstack_erase to disable coverage only on Clang
----------------------------------------------------------------
Kees Cook (4):
staging: media: atomisp: Fix stack buffer overflow in gmin_get_var_int()
kstack_erase: Fix missed export of renamed KSTACK_ERASE_CFLAGS
fortify: Fix incorrect reporting of read buffer size
compiler_types: Provide __no_kstack_erase to disable coverage only on Clang
scripts/Makefile.kstack_erase | 2 +-
arch/x86/include/asm/init.h | 2 +-
include/linux/compiler-clang.h | 3 +++
include/linux/compiler_types.h | 4 ++++
include/linux/fortify-string.h | 2 +-
include/linux/init.h | 2 +-
drivers/staging/media/atomisp/pci/atomisp_gmin_platform.c | 9 +++++----
7 files changed, 16 insertions(+), 8 deletions(-)
--
Kees Cook
next reply other threads:[~2025-07-30 0:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-30 0:29 Kees Cook [this message]
2025-07-30 5:06 ` [GIT PULL] hardening fixes for v6.17-rc1 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=202507291728.51BAA26@keescook \
--to=kees@kernel.org \
--cc=elver@google.com \
--cc=gustavoars@kernel.org \
--cc=hansg@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=nathan@kernel.org \
--cc=syzbot+5245cb609175fb6e8122@syzkaller.appspotmail.com \
--cc=torvalds@linux-foundation.org \
--cc=z3ptaa@gmail.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