From: syzbot <syzbot+703d8a2cd20971854b06@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Forwarded: [PATCH] crypto: adiantum: initialize rbuf.bignum to fix KMSAN uninit-value bug
Date: Tue, 16 Dec 2025 14:52:49 -0800 [thread overview]
Message-ID: <6941e2c1.a70a0220.25eec0.000b.GAE@google.com> (raw)
In-Reply-To: <692f9906.a70a0220.d98e3.01ae.GAE@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: [PATCH] crypto: adiantum: initialize rbuf.bignum to fix KMSAN uninit-value bug
Author: katharasasikumar007@gmail.com
Signed-off-by: Kathara Sasikumar <katharasasikumar007@gmail.com>
#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
---
crypto/adiantum.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/crypto/adiantum.c b/crypto/adiantum.c
index a6bca877c3c7..0803451fdbb7 100644
--- a/crypto/adiantum.c
+++ b/crypto/adiantum.c
@@ -350,6 +350,7 @@ static int adiantum_crypt(struct skcipher_request *req, bool enc)
if (req->cryptlen < BLOCKCIPHER_BLOCK_SIZE)
return -EINVAL;
+ memset(&rctx->rbuf.bignum, 0, sizeof(rctx->rbuf.bignum));
rctx->enc = enc;
/*
--
2.51.0
next prev parent reply other threads:[~2025-12-16 22:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-03 1:57 [syzbot] [crypto?] KMSAN: uninit-value in adiantum_crypt syzbot
2025-12-13 22:47 ` Forwarded: [PATCH] crypto: adiantum: initialize rbuf.bignum to avoid KMSAN warning syzbot
2025-12-16 22:52 ` syzbot [this message]
2025-12-22 15:57 ` Forwarded: Re: KMSAN: uninit-value in adiantum_crypt syzbot
2026-01-12 19:39 ` [syzbot] [crypto?] " Eric Biggers
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=6941e2c1.a70a0220.25eec0.000b.GAE@google.com \
--to=syzbot+703d8a2cd20971854b06@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.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