1225423 – (CVE-2021-47487) VUL-0: REJECTED: CVE-2021-47487: kernel: drm/amdgpu: fix out of bounds write

Bug 1225423 (CVE-2021-47487) - VUL-0: REJECTED: CVE-2021-47487: kernel: drm/amdgpu: fix out of bounds write

Summary: VUL-0: REJECTED: CVE-2021-47487: kernel: drm/amdgpu: fix out of bounds write

Status:	RESOLVED DUPLICATE of bug 1191949

Alias:	CVE-2021-47487

Product:	SUSE Security Incidents
Classification:	Novell Products
Component:	Incidents (show other bugs)
Version:	unspecified
Hardware:	Other Other

Priority:	P3 - Medium Severity: Normal
Target Milestone:	---
Assignee:	Kernel Bugs
QA Contact:	Security Team bot

URL:	https://smash.suse.de/issue/407365/
Whiteboard:	CVSSv3.1:SUSE:CVE-2021-47487:5.5:(AV:...
Keywords:

Depends on:
Blocks:

Clone This Bug

Reported:	2024-05-28 07:13 UTC by SMASH SMASH
Modified:	2024-05-29 06:50 UTC (History)
CC List:	1 user (show)

See Also:
Found By:	Security Response Team
Services Priority:
Business Priority:
Blocker:	---
Marketing QA Status:	---
IT Deployment:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description SMASH SMASH 2024-05-28 07:13:25 UTC

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

drm/amdgpu: fix out of bounds write

Size can be any value and is user controlled resulting in overwriting the
40 byte array wr_buf with an arbitrary length of data from buf.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2021-47487
https://www.cve.org/CVERecord?id=CVE-2021-47487
https://git.kernel.org/stable/c/5afa7898ab7a0ec9c28556a91df714bf3c2f725e
https://git.kernel.org/stable/c/d3ed72495a59fbfb9377450c8dfe94389a6509a7
https://git.kernel.org/stable/c/eb3b6805e3e9d98b2507201fd061a231988ce623
https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2021/CVE-2021-47487.mbox
https://bugzilla.redhat.com/show_bug.cgi?id=2282933

Comment 2 Thomas Leroy 2024-05-29 06:50:59 UTC

CVE-2021-47487 was rejected

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