linux-kernel - [BUG] sound/core/seq: A possible sleep-in-atomic bug in snd_virmidi_dev_receive

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <a3e0863a-c47e-de76-828d-2dcd4b2b18a0@163.com>
Date:   Mon, 9 Oct 2017 10:42:15 +0800
From:   Jia-Ju Bai <baijiaju1990@....com>
To:     perex@...ex.cz, tiwai@...e.com, o-takashi@...amocchi.jp,
        mingo@...nel.org, danielmentz@...gle.com
Cc:     alsa-devel@...a-project.org, linux-kernel@...r.kernel.org
Subject: [BUG] sound/core/seq: A possible sleep-in-atomic bug in
 snd_virmidi_dev_receive_event

According to seq_virmidi.c, the driver may sleep under a read spinlock.
The function call path is:
snd_virmidi_dev_receive_event (acquire the spinlock)
   snd_seq_dump_var_event
     copy_from_user --> may sleep

This bug is found by my static analysis tool and my code review.


Thanks,
Jia-Ju Bai