linux-kernel - Re: [syzbot] [usb?] INFO: task hung in i2c_tiny_usb

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: <a53fa501-dff1-4732-92c1-fab8e66ef886@suse.com>
Date: Tue, 13 Jan 2026 21:23:14 +0100
From: Oliver Neukum <oneukum@...e.com>
To: weipeng <coderlogicwei@...il.com>
Cc: anna-maria@...utronix.de, frederic@...nel.org,
 linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org,
 syzkaller-bugs@...glegroups.com, tglx@...utronix.de
Subject: Re: [syzbot] [usb?] INFO: task hung in i2c_tiny_usb_disconnect

Hi,

On 13.01.26 16:47, weipeng wrote:
   
> @@ -287,9 +321,12 @@ static void i2c_tiny_usb_disconnect(struct usb_interface *interface)
>   {
>   	struct i2c_tiny_usb *dev = usb_get_intfdata(interface);
>   
> -	i2c_del_adapter(&dev->adapter);
> +	mutex_lock(&dev->usb_lock);
>   	usb_set_intfdata(interface, NULL);
> -	i2c_tiny_usb_free(dev);
> +	dev->disconnected = true;
> +	mutex_unlock(&dev->usb_lock);
> +
> +	queue_work(system_long_wq, &dev->release_work);
>   
>   	dev_dbg(&interface->dev, "disconnected\n");
>   }

what prevents the following sequence:

i2c_tiny_usb_disconnect() -> module unload -> i2c_tiny_usb_release()

As far as I can tell, this can happen and you'd execute already
freed memory.

	Regards
		Oliver