All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: David Howells <dhowells@redhat.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	"David S. Miller" <davem@davemloft.net>,
	James Bottomley <James.Bottomley@hansenpartnership.com>,
	Mimi Zohar <zohar@linux.ibm.com>,
	Eric Biggers <ebiggers@kernel.org>,
	keyrings@vger.kernel.org, linux-integrity@vger.kernel.org,
	linux-security-module@vger.kernel.org
Subject: [GIT PULL] KEYS: changes for v7.4-rc3
Date: Mon, 9 Nov 2026 18:53:42 +0200	[thread overview]
Message-ID: <avH6lqK4nq9j5aKs@kernel.org> (raw)

The following changes since commit 05441d697f7f9a927264f4058cbbc6a03dfcac9d:

  Merge tag 'cocci-7.4-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/jlawall/linux (2026-11-03 08:36:32 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git tags/keys-v7.4-rc3

for you to fetch changes up to 51bcd09b9ffca7a2a3b66fb57182bb391364f612:

  KEYS: Protect the update method check against type removal (2026-11-05 19:19:36 +0200)

----------------------------------------------------------------
[GIT PULL] KEYS: changes for v7.4-rc3

The first three bug fixes are side-products of the rhashtable work, which

1. Expand key->datalen and key->quotalen in order to avoid integer
   truncation and the leak of quota.
2. Enforce KEY_MAX_DESC_SIZE limits across in-kernel and payload-generated
   paths.
3. Verify the key identity in __key_unlink_begin() as type and description
   could also refer to a more recently linked key with matching properties
   as the one being unlinked.

51bcd09b9ffc ("KEYS: Protect the update method check against type removal")
highlights the disperancy of being able to remove key types while keys of
that type still exist.

As a consequence, I've implemented a patch series, which pins the key types to
their LKMs, and removes key_type_dead related keyring GC functionality as the
net result:

https://lore.kernel.org/keyrings/20261108222719.304712-1-jarkko@kernel.org/

Signed-off-by: Jarkko Sakkinen <jarkko@kernel.org>

----------------------------------------------------------------
Cen Zhang (1):
      KEYS: Protect the update method check against type removal

Jarkko Sakkinen (3):
      KEYS: Expand key->{datalen,quotalen} to unsigned int
      KEYS: Reject descriptions larger than KEY_MAX_DESC_SIZE
      KEYS: Verify the key identity in __key_unlink_begin

 fs/smb/client/cifsacl.c     |  6 +++---
 include/linux/key.h         |  7 +++++--
 security/keys/key.c         | 26 ++++++++++++++++++--------
 security/keys/keyctl.c      |  2 --
 security/keys/keyring.c     | 13 ++++++++++++-
 security/keys/request_key.c | 14 ++++++++++++--
 6 files changed, 50 insertions(+), 18 deletions(-)

             reply	other threads:[~2026-11-09 16:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-09 16:53 Jarkko Sakkinen [this message]
2026-11-09 16:55 ` [GIT PULL] KEYS: changes for v7.4-rc3 Jarkko Sakkinen
2026-11-10  0:43 ` 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=avH6lqK4nq9j5aKs@kernel.org \
    --to=jarkko@kernel.org \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=davem@davemloft.net \
    --cc=dhowells@redhat.com \
    --cc=ebiggers@kernel.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=keyrings@vger.kernel.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=zohar@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.