From: Takashi Iwai <tiwai@suse.de>
To: syzbot <syzbot+8f2612936028bfd28f28@syzkaller.appspotmail.com>
Cc: alsa-devel@alsa-project.org, wang6495@umn.edu,
yuehaibing@huawei.com, gregkh@linuxfoundation.org,
tiwai@suse.com, syzkaller-bugs@googlegroups.com,
linux-kernel@vger.kernel.org, glider@google.com,
allison@lohutok.net, tglx@linutronix.de, benquike@gmail.com,
dan.carpenter@oracle.com
Subject: Re: [alsa-devel] KMSAN: uninit-value in get_term_name
Date: Mon, 28 Oct 2019 14:13:20 +0100 [thread overview]
Message-ID: <s5hr22xau8f.wl-tiwai@suse.de> (raw)
In-Reply-To: <000000000000f838060595f602a7@google.com>
On Mon, 28 Oct 2019 11:32:07 +0100,
syzbot wrote:
>
> Uninit was stored to memory at:
> kmsan_save_stack_with_flags mm/kmsan/kmsan.c:151 [inline]
> kmsan_internal_chain_origin+0xbd/0x180 mm/kmsan/kmsan.c:319
> __msan_chain_origin+0x6b/0xd0 mm/kmsan/kmsan_instr.c:179
> parse_term_proc_unit+0x73d/0x7e0 sound/usb/mixer.c:896
> __check_input_term+0x13ef/0x2360 sound/usb/mixer.c:989
So this comes from the invalid descriptor for a processing unit, and
it's very likely the same issue as already spotted -- the validator up
to 5.3-rc4 had a bug that passed the invalid descriptor falsely.
This should have been covered by 5.3-rc5, commit ba8bf0967a15 ("ALSA:
usb-audio: Fix copy&paste error in the validator").
thanks,
Takashi
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2019-10-28 13:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-28 10:32 [alsa-devel] KMSAN: uninit-value in get_term_name syzbot
2019-10-28 13:13 ` Takashi Iwai [this message]
2019-10-28 13:17 ` Alexander Potapenko
2019-10-28 13:30 ` Greg KH
2019-10-28 13:55 ` Takashi Iwai
2019-10-28 14:40 ` Greg KH
2019-11-11 8:57 ` Greg KH
2019-10-28 13:38 ` Andrey Konovalov
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=s5hr22xau8f.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=allison@lohutok.net \
--cc=alsa-devel@alsa-project.org \
--cc=benquike@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=glider@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+8f2612936028bfd28f28@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=tiwai@suse.com \
--cc=wang6495@umn.edu \
--cc=yuehaibing@huawei.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