linux-kernel - BUG: return from function without mutex_unlock in drivers/media/video/cx231xx/cx231xx-core.c

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: <201012131936.13172.strakh@ispras.ru>
Date:	Mon, 13 Dec 2010 19:35:22 +0300
From:	Alexander Strakh <strakh@...ras.ru>
To:	linux-kernel@...r.kernel.org, linux-media@...r.kernel.org,
	Andy Walls <awalls@...metrocast.net>
Subject: BUG: return from function without mutex_unlock   in drivers/media/video/cx231xx/cx231xx-core.c

	KERNEL_VERSION: 2.6.36
        SUBJECT: return from function without mutex_unlock   in 
drivers/media/video/cx231xx/cx231xx-core.c 

        SUBSCRIBE:
1.  In line 282 in function cx231xx_read_ctrl_reg mutex was locked.
2.  If usb_control_msg returns ret<0 then we exit from function 
cx231xx_read_ctrl_reg without unlocking mutex. In other (ret>=0) case mutex 
has been unlocked before exiting in line 295.

 282        mutex_lock(&dev->ctrl_urb_lock);
 283        ret = usb_control_msg(dev->udev, pipe, req,
 284                              USB_DIR_IN | USB_TYPE_VENDOR | 
USB_RECIP_DEVICE,
 285                              val, reg, dev->urb_buf, len, HZ);
 286        if (ret < 0) {
 287                cx231xx_isocdbg(" failed!\n");
 288                /* mutex_unlock(&dev->ctrl_urb_lock); */
 289                return ret;
 290        }
 291
 292        if (len)
 293                memcpy(buf, dev->urb_buf, len);
 294
 295        mutex_unlock(&dev->ctrl_urb_lock);

Found by Linux Device Drivers Verification Project
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/