linux-kernel - Re: possible deadlock in io_poll_double

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-prev] [day] [month] [year] [list]

Message-ID: <54a4b5b1-c527-813b-128d-e0ccc51db4a4@kernel.dk>
Date:   Tue, 30 Aug 2022 07:58:13 -0600
From:   Jens Axboe <axboe@...nel.dk>
To:     Jiacheng Xu <578001344xu@...il.com>, linux-kernel@...r.kernel.org,
        asml.silence@...il.com, Qiang.Zhang@...driver.com
Cc:     io-uring@...r.kernel.org
Subject: Re: possible deadlock in io_poll_double_wake

On 8/30/22 7:33 AM, Jiacheng Xu wrote:
> Hello,
> 
> When using modified Syzkaller to fuzz the Linux kernel-5.19, the
> following crash was triggered. Though the issue seems to get fixed on
> syzbot(https://syzkaller.appspot.com/bug?id=12e4415bf5272f433acefa690478208f3be3be2d),
> it could still be triggered with the following repro.
> We would appreciate a CVE ID if this is a security issue.

It's not, and in any case, the kernel has nothing to do with CVEs.

> HEAD commit: 568035b01cfb Linux-5.15.58
> git tree: upstream
> 
> console output:
> https://drive.google.com/file/d/1e4DHaUKhY9DLZJK_pNScWHydUv-MaD9_/view?usp=sharing
> https://drive.google.com/file/d/1NmOGWcfPnY2kSrS0nOwvG1AZ923jFQ3p/view?usp=sharing
> kernel config: https://drive.google.com/file/d/1wgIUDwP5ho29AM-K7HhysSTfWFpfXYkG/view?usp=sharing
> syz repro: https://drive.google.com/file/d/1e5xY8AOMimLbpAlOOupmGYC_tUA3sa8k/view?usp=sharing
> C reproducer: https://drive.google.com/file/d/1esAe__18Lt7and43QdXFfI6GJCsF85_z/view?usp=sharing
> 
> Description:
> spin_lock_irqsave() in __wake_up_common_lock() is called before waking
> up a task. However, spin_lock_irqsave() has to be called once in
> io_poll_double_wake().
> such call stack is:
> 
>    snd_pcm_post_stop()
>       __wake_up_common_lock()
>          spin_lock_irqsave()
>              io_poll_double_wake()
>                  spin_lock_irqsave()

Please prove that this is actually trying to lock the same waitq.

-- 
Jens Axboe