From: Herbert Xu <herbert@gondor.apana.org.au>
To: Linus Torvalds <torvalds@linux-foundation.org>,
"David S. Miller" <davem@davemloft.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>
Subject: [GIT PULL] Crypto Fixes for 6.18
Date: Fri, 10 Oct 2025 19:39:00 +0800 [thread overview]
Message-ID: <aOjwVEx6xDDRKiAx@gondor.apana.org.au> (raw)
Hi Linus:
The following changes since commit c0d36727bf39bb16ef0a67ed608e279535ebf0da:
crypto: rng - Ensure set_ent is always present (2025-10-06 10:17:07 +0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git tags/v6.18-p3
for you to fetch changes up to 6bb73db6948c2de23e407fe1b7ef94bf02b7529f:
crypto: essiv - Check ssize for decryption and in-place encryption (2025-10-09 15:02:35 +0800)
----------------------------------------------------------------
This push contains the following changes:
- Fix bug in crypto_skcipher that breaks the new ti driver.
- Check for invalid assoclen in essiv.
----------------------------------------------------------------
Herbert Xu (1):
crypto: essiv - Check ssize for decryption and in-place encryption
T Pratham (1):
crypto: skcipher - Fix reqsize handling
crypto/essiv.c | 14 ++++++--------
crypto/skcipher.c | 2 ++
2 files changed, 8 insertions(+), 8 deletions(-)
Thanks,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next reply other threads:[~2025-10-10 12:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-10 11:39 Herbert Xu [this message]
2025-10-10 18:25 ` pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2025-11-14 10:15 Herbert Xu
2025-11-14 18:20 ` pr-tracker-bot
2025-10-31 9:20 Herbert Xu
2025-10-31 14:49 ` pr-tracker-bot
2025-10-08 3:38 Herbert Xu
2025-10-08 18:49 ` 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=aOjwVEx6xDDRKiAx@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=davem@davemloft.net \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®