From: Kees Cook <kees@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Andy Shevchenko <andy@kernel.org>,
Kees Cook <kees@kernel.org>,
Kriish Sharma <kriish.sharma2006@gmail.com>,
Miguel Ojeda <ojeda@kernel.org>,
Nathan Chancellor <nathan@kernel.org>
Subject: [GIT PULL] hardening updates for v6.19-rc1
Date: Tue, 2 Dec 2025 12:02:09 -0800 [thread overview]
Message-ID: <202512021158.AE1C9BB38@keescook> (raw)
Hi Linus,
Please pull these handful of hardening updates for v6.19-rc1. The
random driver fixes are to correct some accidentally wrong types used in
allocations (that didn't affect the resulting size) that never got
picked up from the batch I sent a few months ago. The Makefile change is
to enable better GCC diagnostics for the value range tracking, so we can
get better visibility into where those values are coming from when we
get out-of-bounds warnings at compile time.
Thanks!
-Kees
The following changes since commit 211ddde0823f1442e4ad052a2f30f050145ccada:
Linux 6.18-rc2 (2025-10-19 15:19:16 -1000)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/hardening-v6.19-rc1
for you to fetch changes up to 7454048db27d685a155aaf4ea03bb9ad0d086bb9:
kbuild: Enable GCC diagnostic context for value-tracking warnings (2025-11-24 12:44:05 -0800)
----------------------------------------------------------------
hardening updates for v6.19-rc1
- string: Add missing kernel-doc return descriptions (Kriish Sharma)
- Update some mis-typed allocations
- Enable GCC diagnostic context for value-tracking warnings
----------------------------------------------------------------
Kees Cook (4):
comedi: Adjust range_table_list allocation type
drm/plane: Remove const qualifier from plane->modifiers allocation type
media: iris: Cast iris_hfi_gen2_get_instance() allocation type
kbuild: Enable GCC diagnostic context for value-tracking warnings
Kriish Sharma (1):
string: Add missing kernel-doc return descriptions
Makefile | 3 +++
include/linux/string.h | 7 +++++++
drivers/comedi/drivers/ni_670x.c | 2 +-
drivers/gpu/drm/drm_plane.c | 2 +-
drivers/media/platform/qcom/iris/iris_hfi_gen2_command.c | 2 +-
5 files changed, 13 insertions(+), 3 deletions(-)
--
Kees Cook
next reply other threads:[~2025-12-02 20:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-02 20:02 Kees Cook [this message]
2025-12-05 19:00 ` 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=202512021158.AE1C9BB38@keescook \
--to=kees@kernel.org \
--cc=andy@kernel.org \
--cc=kriish.sharma2006@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=ojeda@kernel.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®