linux-kernel - [BUG] sbni: a possible sleep-in-atomic bug in sbni

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

Message-ID: <571ba417-9419-5e60-db59-aa642a7e9450@gmail.com>
Date:   Tue, 12 Dec 2017 16:53:32 +0800
From:   Jia-Ju Bai <baijiaju1990@...il.com>
To:     davem@...emloft.net, keescook@...omium.org, dhowells@...hat.com,
        timofeev@...nch.ru
Cc:     netdev@...r.kernel.org,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: [BUG] sbni: a possible sleep-in-atomic bug in sbni_close

According to drivers/net/wan/sbni.c, the driver may sleep under a spinlock.
The function call path is:
sbni_close (acquire the spinlock)
   free_irq --> may sleep

I do not find a good way to fix it, so I only report.
This possible bug is found by my static analysis tool (DSAC) and checked 
by my code review.

Thanks,
Jia-Ju Bai