Linux s390 Architecture development
 help / color / mirror / Atom feed
From: Vasily Gorbik <gor@linux.ibm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Heiko Carstens <hca@linux.ibm.com>,
	Alexander Gordeev <agordeev@linux.ibm.com>,
	linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org
Subject: [GIT PULL] s390 updates for 7.2-rc6
Date: Sun, 2 Aug 2026 16:16:09 +0200	[thread overview]
Message-ID: <ttj5bmx@ub.hpns> (raw)

Hello Linus,

please pull s390 fixes for 7.2-rc6.

Thank you,
Vasily

The following changes since commit 49145bce539117db4b6e9e83c0e5ef528e361050:

  s390/perf_cpum_cf: Add missing array_index_nospec() to __hw_perf_event_init() (2026-07-15 17:35:42 +0200)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git tags/s390-7.2-6

for you to fetch changes up to 01476391aecef36a3b789ee844357b22fbc90665:

  s390/zcrypt: Fix missing mem scrub at clear key import in cca_clr2cipherkey() (2026-07-31 13:31:20 +0200)

----------------------------------------------------------------
s390 updates for 7.2-rc6

- Fix PCI MMIO write syscall falsely reporting success for mappings not
  valid for MMIO when MIO is unavailable by returning -EFAULT

- Fix CPRB parameter buffer overflows in zcrypt CCA AES cipher and ECC
  private key conversion by rejecting oversized key tokens

- Fix buffer overreads and length underflow in pkey and zcrypt CCA token
  validation by checking length fields against actual buffer sizes

- Fix out of bounds permission bitmap access in zcrypt EP11 admin CPRB
  filtering on custom device nodes by using AP_DOMAINS as the limit

- Fix speculative permission bitmap reads in zcrypt CCA and EP11 admin
  CPRB handling by sanitizing user controlled domain indexes

- Fix sensitive key material left in zcrypt CCA clear key import buffers
  by scrubbing CPRB and temporary buffers after use

----------------------------------------------------------------
Harald Freudenberger (4):
      s390/zcrypt: Fix buffer over-read in cca_cipher2protkey
      s390/zcrypt: Fix wrong domain value verification with EP11 CPRBs
      s390/zcrypt: Close speculative mem read possibility
      s390/zcrypt: Fix missing mem scrub at clear key import in cca_clr2cipherkey()

Holger Dengler (2):
      s390/zcrypt: Validate length for CCA AES cipher key requests
      s390/zcrypt: Validate length for CCA ECC private key requests

Niklas Schnelle (1):
      s390/pci: Fix s390_pci_mmio_write syscall error return without MIO

 arch/s390/pci/pci_mmio.c             |  1 +
 drivers/s390/crypto/pkey_cca.c       | 15 ++----
 drivers/s390/crypto/zcrypt_api.c     |  4 +-
 drivers/s390/crypto/zcrypt_ccamisc.c | 89 +++++++++++++++++++++++++++++-------
 drivers/s390/crypto/zcrypt_ccamisc.h |  6 +--
 5 files changed, 85 insertions(+), 30 deletions(-)

             reply	other threads:[~2026-08-02 14:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-02 14:16 Vasily Gorbik [this message]
2026-08-02 19:30 ` [GIT PULL] s390 updates for 7.2-rc6 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=ttj5bmx@ub.hpns \
    --to=gor@linux.ibm.com \
    --cc=agordeev@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.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