From: Jarkko Sakkinen <jarkko@kernel.org>
To: Michael Bommarito <michael.bommarito@gmail.com>
Cc: David Howells <dhowells@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Paul Moore <paul@paul-moore.com>,
James Morris <jmorris@namei.org>,
"Serge E . Hallyn" <serge@hallyn.com>,
keyrings@vger.kernel.org, linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] keys: fix out-of-bounds read in keyring_get_key_chunk()
Date: Sat, 18 Jul 2026 21:36:41 +0300 [thread overview]
Message-ID: <alvHuX78xVfyYclS@kernel.org> (raw)
In-Reply-To: <20260714115451.3773164-2-michael.bommarito@gmail.com>
On Tue, Jul 14, 2026 at 07:54:49AM -0400, Michael Bommarito wrote:
> For description-level chunks keyring_get_key_chunk() advances the read
> pointer by level * sizeof(long) past the inline prefix but only
> bounds-checks the prefix, so a long enough key description is read past
> its kmemdup(desc, desc_len + 1) allocation. Compute the full byte
> offset and bounds-check the description against it before reading.
>
> The walk only reaches a description-level chunk when two keys collide
> through the hash, x, type and domain_tag chunks, so this is reached from
> an unprivileged add_key(2) with a crafted pair of same-type keys whose
> index hashes collide; KASAN reports a slab-out-of-bounds read.
>
> Fixes: f771fde82051 ("keys: Simplify key description management")
> Assisted-by: Claude:claude-opus-4-8
> Signed-off-by: Michael Bommarito <michael.bommarito@gmail.com>
> ---
> security/keys/keyring.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> KASAN, x86_64: add_key(2) of a crafted hash-colliding "user"-key pair
> (~63-byte descriptions) reports
>
> BUG: KASAN: slab-out-of-bounds in keyring_get_key_chunk
> keyring_get_key_chunk <- assoc_array_insert <- __key_link_begin
> <- __do_sys_add_key
>
> reading one byte past the description allocation; the same trigger is
> KASAN-clean with this patch. On a kernel built without init-on-alloc,
> reading the colliding keyring back with KEYCTL_READ returns
> uninitialized slab until patches 2 and 3 are applied too. Trigger
> available off-list.
>
> diff --git a/security/keys/keyring.c b/security/keys/keyring.c
> index 7a2ee0ded7c93..1739373172ad5 100644
> --- a/security/keys/keyring.c
> +++ b/security/keys/keyring.c
> @@ -270,7 +270,7 @@ static unsigned long keyring_get_key_chunk(const void *data, int level)
> const struct keyring_index_key *index_key = data;
> unsigned long chunk = 0;
> const u8 *d;
> - int desc_len = index_key->desc_len, n = sizeof(chunk);
> + int desc_len = index_key->desc_len, n = sizeof(chunk), offset;
>
> level /= ASSOC_ARRAY_KEY_CHUNK_SIZE;
> switch (level) {
> @@ -284,12 +284,12 @@ static unsigned long keyring_get_key_chunk(const void *data, int level)
> return (unsigned long)index_key->domain_tag;
> default:
> level -= 4;
> - if (desc_len <= sizeof(index_key->desc))
> + offset = sizeof(index_key->desc) + level * sizeof(long);
> + if (desc_len <= offset)
> return 0;
>
> - d = index_key->description + sizeof(index_key->desc);
> - d += level * sizeof(long);
> - desc_len -= sizeof(index_key->desc);
> + d = index_key->description + offset;
> + desc_len -= offset;
> if (desc_len > n)
> desc_len = n;
> do {
> --
> 2.53.0
>
Same feedback as before.
BR, Jarkko
next prev parent reply other threads:[~2026-07-18 18:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 11:54 [PATCH v2 0/3] keys: fix keyring assoc-array out-of-bounds read and index inconsistency Michael Bommarito
2026-07-14 11:54 ` [PATCH v2 1/3] keys: fix out-of-bounds read in keyring_get_key_chunk() Michael Bommarito
2026-07-18 18:36 ` Jarkko Sakkinen [this message]
2026-07-14 11:54 ` [PATCH v2 2/3] keys: make keyring key-chunk byte order agree with keyring_diff_objects() Michael Bommarito
2026-07-18 18:36 ` Jarkko Sakkinen
2026-07-14 11:54 ` [PATCH v2 3/3] assoc_array: trim the final shortcut word using the current chunk end Michael Bommarito
2026-07-18 18:37 ` Jarkko Sakkinen
2026-07-18 18:46 ` Jarkko Sakkinen
2026-07-18 20:35 ` Michael Bommarito
2026-07-18 22:18 ` Jarkko Sakkinen
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=alvHuX78xVfyYclS@kernel.org \
--to=jarkko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=jmorris@namei.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=michael.bommarito@gmail.com \
--cc=paul@paul-moore.com \
--cc=serge@hallyn.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
Powered by JetHome