general protection fault in lock_sock_nested

Status: auto-closed as invalid on 2021/09/04 19:35
Reported-by: syzbot+e50791b307d00c5cf534@syzkaller.appspotmail.com
First crash: 2187d, last: 1969d
▶ ▼ Similar bugs (17)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
android-49 general protection fault in lock_sock_nested 2 1 3151d 3151d 0/3 auto-closed as invalid on 2019/02/22 12:39
upstream general protection fault in lock_sock_nested prio:high bluetooth 19 syz, C done done 4503 107d 1113d 0/29 upstream: reported C repro on 2023/09/11 07:52
linux-5.15 general protection fault in lock_sock_nested missing-backport origin:upstream 8 syz, C error 158 171d 906d 0/3 upstream: reported C repro on 2024/04/04 13:25
linux-6.1 general protection fault in lock_sock_nested origin:upstream missing-backport 19 syz, C inconclusive 240 164d 897d 0/3 upstream: reported C repro on 2024/04/14 08:46
linux-6.6 general protection fault in lock_sock_nested 2 syz, C error 34 177d 466d 0/2 auto-obsoleted due to no activity on 2026/07/12 13:28
upstream BUG: unable to handle kernel paging request in lock_sock_nested bluetooth 17 43 1804d 2244d 0/29 auto-closed as invalid on 2022/02/16 22:16
linux-4.19 KASAN: wild-memory-access Write in lock_sock_nested 21 2 2068d 2137d 0/1 auto-closed as invalid on 2021/05/28 14:35
linux-6.1 BUG: sleeping function called from invalid context in lock_sock_nested (2) origin:upstream missing-backport 22 syz, C inconclusive 15 168d 582d 0/3 upstream: reported C repro on 2025/02/23 00:56
linux-4.19 KASAN: use-after-free Read in lock_sock_nested 21 syz, C 471 1307d 2620d 0/1 upstream: reported C repro on 2019/07/26 21:27
linux-4.14 KASAN: use-after-free Read in lock_sock_nested 19 syz, C inconclusive 331 1347d 2714d 0/1 upstream: reported C repro on 2019/04/24 06:28
upstream KASAN: use-after-free Read in lock_sock_nested hams 19 syz, C inconclusive done 1856 1216d 2825d 0/29 auto-obsoleted due to no activity on 2023/08/23 09:06
linux-6.1 BUG: sleeping function called from invalid context in lock_sock_nested 5 7 800d 821d 0/3 auto-obsoleted due to no activity on 2024/10/28 05:57
linux-4.14 BUG: unable to handle kernel paging request in lock_sock_nested 8 4 1962d 2082d 0/1 auto-closed as invalid on 2021/09/11 11:51
upstream KASAN: slab-out-of-bounds Read in lock_sock_nested bluetooth 17 syz unreliable done 23 1798d 2238d 0/29 auto-obsoleted due to no activity on 2022/09/29 10:19
linux-4.19 KASAN: slab-out-of-bounds Read in lock_sock_nested 21 14 1481d 2145d 0/1 auto-obsoleted due to no activity on 2023/01/05 15:59
upstream BUG: sleeping function called from invalid context in lock_sock_nested (3) bluetooth 19 syz, C inconclusive error 153 389d 867d 0/29 auto-obsoleted due to no activity on 2025/11/12 14:25
linux-5.15 BUG: sleeping function called from invalid context in lock_sock_nested missing-backport origin:lts-only 19 syz, C done 25 117d 821d 0/3 auto-obsoleted due to no activity on 2026/09/10 15:07

Sample crash report:
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] PREEMPT SMP KASAN
Modules linked in:
CPU: 0 PID: 3622 Comm: kworker/0:2 Not tainted 4.14.232-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: events l2cap_chan_timeout
task: ffff8880a8e342c0 task.stack: ffff8880a8e48000
RIP: 0010:atomic_inc arch/x86/include/asm/atomic.h:92 [inline]
RIP: 0010:__lock_acquire+0x21e/0x3f20 kernel/locking/lockdep.c:3382
RSP: 0018:ffff8880a8e4f9a8 EFLAGS: 00010086
RAX: dead4ead00000000 RBX: 0000000000000000 RCX: 0000000000000000
RDX: 1ffff110096f4295 RSI: 0000000000000000 RDI: ffff88804b7a14a8
RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000001 R11: ffff8880a8e342c0 R12: ffff88804b7a14a0
R13: 0000000000000000 R14: 0000000000000000 R15: ffffffff8bebbd40
FS:  0000000000000000(0000) GS:ffff8880ba400000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055c67eb122c8 CR3: 0000000052483000 CR4: 00000000001426f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 lock_acquire+0x170/0x3f0 kernel/locking/lockdep.c:3998
 __raw_spin_lock_bh include/linux/spinlock_api_smp.h:135 [inline]
 _raw_spin_lock_bh+0x2f/0x40 kernel/locking/spinlock.c:176
 spin_lock_bh include/linux/spinlock.h:322 [inline]
 lock_sock_nested+0x39/0x100 net/core/sock.c:2788
 l2cap_sock_teardown_cb+0x93/0x650 net/bluetooth/l2cap_sock.c:1341
 l2cap_chan_del+0xaf/0x950 net/bluetooth/l2cap_core.c:599
 l2cap_chan_close+0x103/0x870 net/bluetooth/l2cap_core.c:757
 l2cap_chan_timeout+0x143/0x2a0 net/bluetooth/l2cap_core.c:430
 process_one_work+0x793/0x14a0 kernel/workqueue.c:2116
 worker_thread+0x5cc/0xff0 kernel/workqueue.c:2250
 kthread+0x30d/0x420 kernel/kthread.c:232
 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:404
Code: 00 fc ff df 41 89 f6 4b 8d 7c f4 08 48 89 fa 48 c1 ea 03 80 3c 02 00 0f 85 5e 2a 00 00 4b 8b 44 f4 08 48 85 c0 0f 84 31 ff ff ff <f0> ff 80 38 01 00 00 49 8d b3 80 08 00 00 48 ba 00 00 00 00 00 
RIP: atomic_inc arch/x86/include/asm/atomic.h:92 [inline] RSP: ffff8880a8e4f9a8
RIP: __lock_acquire+0x21e/0x3f20 kernel/locking/lockdep.c:3382 RSP: ffff8880a8e4f9a8
---[ end trace b6e24dfe011af0ef ]---

Crashes (4):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2021/05/07 19:35 linux-4.14.y 7d7d1c0ab3eb f6da8120 .config console log report info ci2-linux-4-14 general protection fault in lock_sock_nested
2021/01/30 09:49 linux-4.14.y 2d2791fce891 fc9fd31e .config console log report info ci2-linux-4-14 general protection fault in lock_sock_nested
2021/01/03 03:43 linux-4.14.y 1752938529c6 79264ae3 .config console log report info ci2-linux-4-14
2020/10/01 19:04 linux-4.14.y cbfa1702aaf6 4103fce0 .config console log report info ci2-linux-4-14
* Struck through repros no longer work on HEAD.