Bug 2239712 (CVE-2020-36766)

Summary:	CVE-2020-36766 kernel: memory leak in drivers/media/cec/core/cec-api.c
Product:	[Other] Security Response	Reporter:	Zack Miele <zmiele>
Component:	vulnerability	Assignee:	Product Security <prodsec-ir-bot>
Status:	NEW ---	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	unspecified	CC:	aazores, acaringi, allarkin, bhu, chazlett, chwhite, dbohanno, debarbos, dfreiber, dvlasenk, eaguilar, ebaron, ezulian, hkrzesin, jarod, jburrell, jdenham, jfaracco, jforbes, jkang, jlelli, joe.lawrence, jpallich, jshortt, jstancek, jwyatt, kcarcia, ldoskova, lgoncalv, lzampier, nmurray, pjindal, ptalbert, rkeshri, rogbas, rrobaina, rvrbovsk, scweaver, sfroberg, tglozar, vkumar, walters, wcosta, williams, wmealing, ycote
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	kernel 5.8.6	Doc Type:	If docs needed, set a value
Doc Text:	A flaw was found in cec_adap_g_log_addrs in drivers/media/cec/core/cec-api.c in the Linux Kernel. This issue may allow a local attacker to leak one byte of kernel memory on specific hardware to unprivileged users, directly assigning log_addrs with a hole in the structure, causing a kernel information leak problem.	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:
Bug Depends On:	2239715
Bug Blocks:	2239714

Description Zack Miele 2023-09-19 19:01:45 UTC

An issue was discovered in the Linux kernel before 5.8.6. drivers/media/cec/core/cec-api.c leaks one byte of kernel memory on specific hardware to unprivileged users, because of directly assigning log_addrs with a hole in the struct.

https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.8.6
https://github.com/torvalds/linux/commit/6c42227c3467549ddc65efe99c869021d2f4a570

Comment 5 Rohit Keshri 2023-09-25 12:21:05 UTC

*** Bug 2239820 has been marked as a duplicate of this bug. ***