From: syzbot <syzbot+aeb14e2539ffb6d21130@syzkaller.appspotmail.com>
To: davem@davemloft.net, herbert@gondor.apana.org.au,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [crypto?] KMSAN: uninit-value in aes_encrypt (5)
Date: Thu, 09 May 2024 21:02:27 -0700 [thread overview]
Message-ID: <00000000000099249d0618119a0c@google.com> (raw)
In-Reply-To: <0000000000000fe556061725a7be@google.com>
syzbot has found a reproducer for the following issue on:
HEAD commit: 45db3ab70092 Merge tag '6.9-rc7-ksmbd-fixes' of git://git...
git tree: upstream
console+strace: https://syzkaller.appspot.com/x/log.txt?x=14d9bfdf180000
kernel config: https://syzkaller.appspot.com/x/.config?x=617171361dd3cd47
dashboard link: https://syzkaller.appspot.com/bug?extid=aeb14e2539ffb6d21130
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1617adb8980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=112f45d4980000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/232e7c2a73a5/disk-45db3ab7.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/7e9bf7c936ab/vmlinux-45db3ab7.xz
kernel image: https://storage.googleapis.com/syzbot-assets/5e8f98ee02d8/bzImage-45db3ab7.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/fcc88c919ed9/mount_1.gz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+aeb14e2539ffb6d21130@syzkaller.appspotmail.com
fscrypt: AES-256-XTS using implementation "xts(ecb(aes-fixed-time))"
=====================================================
BUG: KMSAN: uninit-value in subshift lib/crypto/aes.c:149 [inline]
BUG: KMSAN: uninit-value in aes_encrypt+0x15cc/0x1db0 lib/crypto/aes.c:282
subshift lib/crypto/aes.c:149 [inline]
aes_encrypt+0x15cc/0x1db0 lib/crypto/aes.c:282
aesti_encrypt+0x7d/0xf0 crypto/aes_ti.c:31
crypto_ecb_crypt crypto/ecb.c:23 [inline]
crypto_ecb_encrypt2+0x18a/0x300 crypto/ecb.c:40
crypto_lskcipher_crypt_sg+0x36b/0x7f0 crypto/lskcipher.c:228
crypto_lskcipher_encrypt_sg+0x8a/0xc0 crypto/lskcipher.c:247
crypto_skcipher_encrypt+0x119/0x1e0 crypto/skcipher.c:669
xts_encrypt+0x3c4/0x550 crypto/xts.c:269
crypto_skcipher_encrypt+0x1a0/0x1e0 crypto/skcipher.c:671
fscrypt_crypt_data_unit+0x4ee/0x8f0 fs/crypto/crypto.c:144
fscrypt_encrypt_pagecache_blocks+0x422/0x900 fs/crypto/crypto.c:207
ext4_bio_write_folio+0x13db/0x2e40 fs/ext4/page-io.c:526
mpage_submit_folio+0x351/0x4a0 fs/ext4/inode.c:1869
mpage_process_page_bufs+0xb92/0xe30 fs/ext4/inode.c:1982
mpage_prepare_extent_to_map+0x1702/0x22c0 fs/ext4/inode.c:2490
ext4_do_writepages+0x1117/0x62e0 fs/ext4/inode.c:2632
ext4_writepages+0x312/0x830 fs/ext4/inode.c:2768
do_writepages+0x427/0xc30 mm/page-writeback.c:2612
filemap_fdatawrite_wbc+0x1d8/0x270 mm/filemap.c:397
__filemap_fdatawrite_range mm/filemap.c:430 [inline]
file_write_and_wait_range+0x1bf/0x370 mm/filemap.c:788
generic_buffers_fsync_noflush+0x84/0x3e0 fs/buffer.c:602
ext4_fsync_nojournal fs/ext4/fsync.c:88 [inline]
ext4_sync_file+0x5ba/0x13a0 fs/ext4/fsync.c:151
vfs_fsync_range+0x20d/0x270 fs/sync.c:188
generic_write_sync include/linux/fs.h:2795 [inline]
ext4_buffered_write_iter+0x9ad/0xaa0 fs/ext4/file.c:305
ext4_file_write_iter+0x208/0x3450
call_write_iter include/linux/fs.h:2110 [inline]
new_sync_write fs/read_write.c:497 [inline]
vfs_write+0xb63/0x1520 fs/read_write.c:590
ksys_write+0x20f/0x4c0 fs/read_write.c:643
__do_sys_write fs/read_write.c:655 [inline]
__se_sys_write fs/read_write.c:652 [inline]
__x64_sys_write+0x93/0xe0 fs/read_write.c:652
x64_sys_call+0x3062/0x3b50 arch/x86/include/generated/asm/syscalls_64.h:2
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xcf/0x1e0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
Uninit was stored to memory at:
le128_xor include/crypto/b128ops.h:69 [inline]
xts_xor_tweak+0x4ae/0xbf0 crypto/xts.c:123
xts_xor_tweak_pre crypto/xts.c:135 [inline]
xts_encrypt+0x296/0x550 crypto/xts.c:268
crypto_skcipher_encrypt+0x1a0/0x1e0 crypto/skcipher.c:671
fscrypt_crypt_data_unit+0x4ee/0x8f0 fs/crypto/crypto.c:144
fscrypt_encrypt_pagecache_blocks+0x422/0x900 fs/crypto/crypto.c:207
ext4_bio_write_folio+0x13db/0x2e40 fs/ext4/page-io.c:526
mpage_submit_folio+0x351/0x4a0 fs/ext4/inode.c:1869
mpage_process_page_bufs+0xb92/0xe30 fs/ext4/inode.c:1982
mpage_prepare_extent_to_map+0x1702/0x22c0 fs/ext4/inode.c:2490
ext4_do_writepages+0x1117/0x62e0 fs/ext4/inode.c:2632
ext4_writepages+0x312/0x830 fs/ext4/inode.c:2768
do_writepages+0x427/0xc30 mm/page-writeback.c:2612
filemap_fdatawrite_wbc+0x1d8/0x270 mm/filemap.c:397
__filemap_fdatawrite_range mm/filemap.c:430 [inline]
file_write_and_wait_range+0x1bf/0x370 mm/filemap.c:788
generic_buffers_fsync_noflush+0x84/0x3e0 fs/buffer.c:602
ext4_fsync_nojournal fs/ext4/fsync.c:88 [inline]
ext4_sync_file+0x5ba/0x13a0 fs/ext4/fsync.c:151
vfs_fsync_range+0x20d/0x270 fs/sync.c:188
generic_write_sync include/linux/fs.h:2795 [inline]
ext4_buffered_write_iter+0x9ad/0xaa0 fs/ext4/file.c:305
ext4_file_write_iter+0x208/0x3450
call_write_iter include/linux/fs.h:2110 [inline]
new_sync_write fs/read_write.c:497 [inline]
vfs_write+0xb63/0x1520 fs/read_write.c:590
ksys_write+0x20f/0x4c0 fs/read_write.c:643
__do_sys_write fs/read_write.c:655 [inline]
__se_sys_write fs/read_write.c:652 [inline]
__x64_sys_write+0x93/0xe0 fs/read_write.c:652
x64_sys_call+0x3062/0x3b50 arch/x86/include/generated/asm/syscalls_64.h:2
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xcf/0x1e0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
Uninit was created at:
__alloc_pages+0x9d6/0xe70 mm/page_alloc.c:4598
alloc_pages_mpol+0x299/0x990 mm/mempolicy.c:2264
alloc_pages mm/mempolicy.c:2335 [inline]
folio_alloc+0x1d0/0x230 mm/mempolicy.c:2342
filemap_alloc_folio+0xa6/0x440 mm/filemap.c:984
__filemap_get_folio+0xa10/0x14b0 mm/filemap.c:1926
ext4_write_begin+0x3e5/0x2230 fs/ext4/inode.c:1159
generic_perform_write+0x400/0xc60 mm/filemap.c:3974
ext4_buffered_write_iter+0x564/0xaa0 fs/ext4/file.c:299
ext4_file_write_iter+0x208/0x3450
call_write_iter include/linux/fs.h:2110 [inline]
new_sync_write fs/read_write.c:497 [inline]
vfs_write+0xb63/0x1520 fs/read_write.c:590
ksys_write+0x20f/0x4c0 fs/read_write.c:643
__do_sys_write fs/read_write.c:655 [inline]
__se_sys_write fs/read_write.c:652 [inline]
__x64_sys_write+0x93/0xe0 fs/read_write.c:652
x64_sys_call+0x3062/0x3b50 arch/x86/include/generated/asm/syscalls_64.h:2
do_syscall_x64 arch/x86/entry/common.c:52 [inline]
do_syscall_64+0xcf/0x1e0 arch/x86/entry/common.c:83
entry_SYSCALL_64_after_hwframe+0x77/0x7f
CPU: 0 PID: 5048 Comm: syz-executor132 Not tainted 6.9.0-rc7-syzkaller-00056-g45db3ab70092 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024
=====================================================
---
If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.
next prev parent reply other threads:[~2024-05-10 4:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-28 10:32 [syzbot] [crypto?] KMSAN: uninit-value in aes_encrypt (5) syzbot
2024-05-10 4:02 ` syzbot [this message]
2024-05-30 4:31 ` Herbert Xu
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=00000000000099249d0618119a0c@google.com \
--to=syzbot+aeb14e2539ffb6d21130@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).