Bug 2425032 (CVE-2022-50733)

Summary:	CVE-2022-50733 kernel: usb: idmouse: fix an uninit-value in idmouse_open
Product:	[Other] Security Response	Reporter:	OSIDB Bzimport <bzimport>
Component:	vulnerability	Assignee:	Product Security DevOps Team <prodsec-dev>
Status:	NEW ---	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	unspecified	Keywords:	Security
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	---
Doc Text:	A use of uninitialized memory was found in the Linux kernel's idmouse USB fingerprint reader driver. In idmouse_create_image(), when any ftip_command() fails, control jumps to the reset label but leaves bulk_in_buffer data uninitialized. The subsequent check for a valid image then dereferences this uninitialized data, leading to undefined behavior.	Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description OSIDB Bzimport 2025-12-24 13:03:21 UTC

In the Linux kernel, the following vulnerability has been resolved:

usb: idmouse: fix an uninit-value in idmouse_open

In idmouse_create_image, if any ftip_command fails, it will
go to the reset label. However, this leads to the data in
bulk_in_buffer[HEADER..IMGSIZE] uninitialized. And the check
for valid image incurs an uninitialized dereference.

Fix this by moving the check before reset label since this
check only be valid if the data after bulk_in_buffer[HEADER]
has concrete data.

Note that this is found by KMSAN, so only kernel compilation
is tested.

Comment 1 Alexander B 2025-12-25 07:27:40 UTC

Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2025122421-CVE-2022-50733-a587@gregkh/T