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

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 for Android: free password hash cracker in your pocket

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

Message-ID: <8b0519f9-e5f3-aa73-09be-f399f6a6865a@gmail.com>
Date:   Tue, 12 Dec 2017 17:04:52 +0800
From:   Jia-Ju Bai <baijiaju1990@...il.com>
To:     kvalo@...eaurora.org, mhchen@...f.ccl.itri.org.tw,
        acme@...ectiva.com.br, niemeyer@...ectiva.com
Cc:     linux-wireless@...r.kernel.org, netdev@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: [BUG] wl3501: a possible sleep-in-atomic bug in wl3501_reset

According to drivers/net/wireless/wl3501_cs.c, the driver may sleep 
under a spinlock.
The function call path is:
wl3501_reset (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