Bug 2132639

Summary:	kernel: Use after Free in gru_set_context_option leading to kernel panic
Product:	[Other] Security Response	Reporter:	Alex <allarkin>
Component:	vulnerability	Assignee:	Red Hat Product Security <security-response-team>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	acaringi, adscvr, airlied, alciregi, arachman, bhu, brdeoliv, bskeggs, chwhite, crwood, ctoe, ddepaula, debarbos, dhoward, dvlasenk, ezulian, fhrbata, hdegoede, hkrzesin, hpa, jarod, jarodwilson, jburrell, jfaracco, jferlan, jforbes, jglisse, jlelli, joe.lawrence, jonathan, josef, jpoimboe, jshortt, jstancek, jwboyer, jwyatt, kcarcia, kernel-maint, kernel-mgr, kpatch-maint, lgoncalv, linville, lleshchi, lveyde, lzampier, masami256, mchehab, michal.skrivanek, mperina, nmurray, ptalbert, qzhao, rhandlin, rvrbovsk, sbonazzo, scweaver, steved, tyberry, vkumar, walters, williams, ycote
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-10-06 10:31:02 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:
Bug Blocks:	2126811

Description Alex 2022-10-06 09:55:12 UTC

A use after free flaw in the Linux Kernel SGI GRU driver in drivers/misc/sgi-gru/grufile.c found. A local user can call gru_file_unlocked_ioctl with GRU_SET_CONTEXT_OPTION and then triggering error path in gru_check_context_placement function. This leads to use after free in gru_unload_context function.

Reference:
https://www.spinics.net/lists/kernel/msg4518970.html


Besides, this is a long existing bug which was introduced in 13 years ago:
https://github.com/torvalds/linux/commit/55484c45dbeca2eec7642932ec3f60f8a2d4bdbf

Comment 1 Alex 2022-10-06 10:31:02 UTC


*** This bug has been marked as a duplicate of bug 2132640 ***