Bug 1968057 (CVE-2021-3587)

Summary:	CVE-2021-3587 kernel: nfc: Null pointer dereference in llcp_sock_getname
Product:	[Other] Security Response	Reporter:	Pedro Sampaio <psampaio>
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, bhu, blc, bmasney, brdeoliv, bskeggs, chwhite, crwood, dhoward, dvlasenk, fhrbata, fpacheco, hdegoede, hkrzesin, jarodwilson, jeremy, jforbes, jglisse, jlelli, jonathan, josef, jshortt, jstancek, jwboyer, kcarcia, kernel-maint, kernel-mgr, lgoncalv, linville, masami256, mchehab, mlangsdo, nmurray, ptalbert, qzhao, rvrbovsk, steved, walters, wcosta, williams
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:	A flaw was found in the Linux kernel. A null pointer dereference in llcp_sock_getname in net/nfc/llcp_sock.c can lead to an unprivileged user triggering this bug, causing denial of service.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-08-24 14:48:28 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:	1969289, 1969674
Bug Blocks:	1968059, 1968758

Description Pedro Sampaio 2021-06-04 19:45:53 UTC

There is a null pointer dereference in llcp_sock_getname in net/nfc/llcp_sock.c reproduced in linux-5.13.0-rc2. An unprivileged user can trigger this bug and cause denial of service.

References:

https://seclists.org/oss-sec/2021/q2/177
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=4ac06a1e013c

Comment 2 Wade Mealing 2021-06-08 07:07:43 UTC

Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 1969289]

Comment 10 Petr Matousek 2021-08-24 14:48:28 UTC


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

Comment 11 Wade Mealing 2021-08-25 04:47:04 UTC

For anyone following along, this was a duplicate of: CVE-2021-38208