Bug 2169487

Summary:	kernel: msb_init_disk in drivers/memstick/core/ms_block.c lacks check of the return value of alloc_ordered_workqueue() and will cause the NULL Pointer Dereference or memory leak
Product:	[Other] Security Response	Reporter:	Alex <allarkin>
Component:	vulnerability	Assignee:	Red Hat Product Security <security-response-team>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	unspecified	CC:	acaringi, bhu, chwhite, crwood, ddepaula, debarbos, dfreiber, dhoward, drow, dvlasenk, ezulian, fhrbata, hkrzesin, jarod, jburrell, jfaracco, jferlan, jforbes, jlelli, joe.lawrence, jshortt, jstancek, jwyatt, kcarcia, kernel-mgr, lgoncalv, lleshchi, lzampier, nmurray, ptalbert, qzhao, rogbas, rvrbovsk, scweaver, tyberry, vkumar, walters, williams
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	Linux kernel 6.1-rc8	Doc Type:	If docs needed, set a value
Doc Text:	A null pointer dereference in the Linux kernel MemoryStick Standard device driver was found. A local user could use this flaw to crash the system.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-02-15 06:28:42 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	2169488
Bug Blocks:	2167953

Description Alex 2023-02-13 17:42:51 UTC

An issue was discovered in the Linux kernel through 6.1-rc8.
msb_init_disk in drivers/memstick/core/ms_block.c lacks check of the
return value of alloc_ordered_workqueue() and will cause the
NULL Pointer Dereference. Moreover, the unreleased workqueue will
cause the Memory Leak.

Reference:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4f431a047a5c8698ed4b67e2760cfbeb5fffb69d

Comment 1 Alex 2023-02-13 17:43:15 UTC

Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 2169488]

Comment 3 Justin M. Forbes 2023-03-01 19:34:18 UTC

This was fixed for Fedora with the 6.0.16 stable kernel updates.