summaryrefslogtreecommitdiffstats
path: root/active/CVE-2021-42327
diff options
context:
space:
mode:
authorBen Hutchings <ben@decadent.org.uk>2021-10-27 20:07:37 +0200
committerBen Hutchings <ben@decadent.org.uk>2021-10-27 20:09:38 +0200
commitbb3538ddad18087c0b3ca2d4f8c7405bf197f6f4 (patch)
treed5ef17ea11dea12626469940fc2e71a9b7035f2f /active/CVE-2021-42327
parent97e7746dd6d1df5925f3b8075490c3050dc6e503 (diff)
Fill in status for various issues
Diffstat (limited to 'active/CVE-2021-42327')
-rw-r--r--active/CVE-2021-4232713
1 files changed, 9 insertions, 4 deletions
diff --git a/active/CVE-2021-42327 b/active/CVE-2021-42327
index 29113cfa..a907f5f9 100644
--- a/active/CVE-2021-42327
+++ b/active/CVE-2021-42327
@@ -1,13 +1,18 @@
Description: drm/amdgpu: fix out of bounds write
References:
https://lists.freedesktop.org/archives/amd-gfx/2021-October/070170.html
+ https://cgit.freedesktop.org/drm/drm/commit/?id=f23750b5b3d98653b31d4469592935ef6364ad67
Notes:
+ bwh> Introduced in 5.10 by commit 918698d5c2b5 "drm/amd/display: Return the
+ bwh> number of bytes parsed than allocated". This actually introduced the
+ bwh> same bug in many debugfs write operations in the same source file.
+ bwh> One of these is fixed in drm-next, so should be in upstream 5.16-rc1.
Bugs:
upstream: needed
5.10-upstream-stable: needed
-4.19-upstream-stable:
-4.9-upstream-stable:
+4.19-upstream-stable: N/A "Vulnerability introduced later"
+4.9-upstream-stable: N/A "Vulnerability introduced later"
sid: needed
5.10-bullseye-security: needed
-4.19-buster-security:
-4.9-stretch-security:
+4.19-buster-security: N/A "Vulnerability introduced later"
+4.9-stretch-security: N/A "Vulnerability introduced later"

© 2014-2024 Faster IT GmbH | imprint | privacy policy