From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-64558: s390/pkey: Check length in pkey_pckmo handler implementation
Date: Wed, 29 Jul 2026 18:31:13 +0200 [thread overview]
Message-ID: <2026072912-CVE-2026-64558-7352@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
s390/pkey: Check length in pkey_pckmo handler implementation
Explicitly check the length of the target buffer in the pkey_pckmo
implementation of the key_to_protkey() handler function. The handler
function fails, if the generated output data exceeds the length of the
provided target buffer.
The Linux kernel CVE team has assigned CVE-2026-64558 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.12 with commit 8fcc231ce3bea12b78bb94b280cdc03cff342435 and fixed in 6.12.97 with commit 02028a24e26d85262ab9c8fc4344e1f3503007fc
Issue introduced in 6.12 with commit 8fcc231ce3bea12b78bb94b280cdc03cff342435 and fixed in 6.18.40 with commit 433e5e70cdc1edf382d28d08a885b22e2b98b7da
Issue introduced in 6.12 with commit 8fcc231ce3bea12b78bb94b280cdc03cff342435 and fixed in 7.1.5 with commit 614aa0491c7a190556c2345dddee0b6f5ed90989
Issue introduced in 6.12 with commit 8fcc231ce3bea12b78bb94b280cdc03cff342435 and fixed in 7.2-rc1 with commit 1ac287e2af9a9112fe271427ef45eceb26bce8b4
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-64558
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/s390/crypto/pkey_pckmo.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/02028a24e26d85262ab9c8fc4344e1f3503007fc
https://git.kernel.org/stable/c/433e5e70cdc1edf382d28d08a885b22e2b98b7da
https://git.kernel.org/stable/c/614aa0491c7a190556c2345dddee0b6f5ed90989
https://git.kernel.org/stable/c/1ac287e2af9a9112fe271427ef45eceb26bce8b4
reply other threads:[~2026-07-29 16:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2026072912-CVE-2026-64558-7352@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 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.