From: Hillf Danton <hdanton@sina.com>
To: syzbot <syzbot+e69c25cf38a53d0cf64c@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [usb?] BUG: corrupted list in usb_hcd_link_urb_to_ep (5)
Date: Mon, 5 Jan 2026 12:07:08 +0800 [thread overview]
Message-ID: <20260105040710.1965-1-hdanton@sina.com> (raw)
In-Reply-To: <695a10bc.050a0220.a1b6.0386.GAE@google.com>
> Date: Sat, 03 Jan 2026 23:03:24 -0800
> syzbot has found a reproducer for the following issue on:
>
> HEAD commit: aacb0a6d604a Merge tag 'pmdomain-v6.19-rc3' of git://git.k..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=16578f92580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=a11e0f726bfb6765
> dashboard link: https://syzkaller.appspot.com/bug?extid=e69c25cf38a53d0cf64c
> compiler: gcc (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1627369a580000
#syz test
--- x/drivers/input/misc/cm109.c
+++ y/drivers/input/misc/cm109.c
@@ -562,15 +562,18 @@ static int cm109_input_open(struct input
dev->ctl_data->byte[HID_OR2] = dev->keybit;
dev->ctl_data->byte[HID_OR3] = 0x00;
+ spin_lock_irq(&dev->ctl_submit_lock);
dev->ctl_urb_pending = 1;
- error = usb_submit_urb(dev->urb_ctl, GFP_KERNEL);
+ error = usb_submit_urb(dev->urb_ctl, GFP_ATOMIC);
if (!error) {
dev->open = 1;
+ spin_unlock_irq(&dev->ctl_submit_lock);
return 0;
}
+ dev->ctl_urb_pending = 0;
+ spin_unlock_irq(&dev->ctl_submit_lock);
}
- dev->ctl_urb_pending = 0;
usb_autopm_put_interface(dev->intf);
dev_err(&dev->intf->dev, "%s: usb_submit_urb (urb_ctl) failed %d\n",
--
next prev parent reply other threads:[~2026-01-05 4:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 15:20 [syzbot] [usb?] BUG: corrupted list in usb_hcd_link_urb_to_ep (5) syzbot
2026-01-04 7:03 ` syzbot
2026-01-05 4:07 ` Hillf Danton [this message]
2026-01-05 4:33 ` syzbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260105040710.1965-1-hdanton@sina.com \
--to=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+e69c25cf38a53d0cf64c@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox