diff options
author | Salvatore Bonaccorso <carnil@debian.org> | 2020-06-06 16:04:10 +0200 |
---|---|---|
committer | Salvatore Bonaccorso <carnil@debian.org> | 2020-06-06 16:04:10 +0200 |
commit | 7012a9ac37639438060b1cd5aa01001bc48e8fff (patch) | |
tree | 162c691b70f1e69be1c748bb00db8ff07774231e /active | |
parent | 3e09691eb36b58f3274cd71dbfc8e6db1ca36ec4 (diff) |
Retire CVE-2020-7053
Diffstat (limited to 'active')
-rw-r--r-- | active/CVE-2020-7053 | 21 |
1 files changed, 0 insertions, 21 deletions
diff --git a/active/CVE-2020-7053 b/active/CVE-2020-7053 deleted file mode 100644 index 0a456d1bf..000000000 --- a/active/CVE-2020-7053 +++ /dev/null @@ -1,21 +0,0 @@ -Description: drm/i915: Fix use-after-free when destroying GEM context -References: - https://lore.kernel.org/stable/20200114183937.12224-1-tyhicks@canonical.com/ - https://bugzilla.suse.com/show_bug.cgi?id=1160966 -Notes: - carnil> Issue was (differently) fixed in mainline by commit - carnil> 7dc40713618c ("drm/i915: Introduce a mutex for file_priv- - carnil> >context_idr") as part of a more complex patch which is part of - carnil> 5.2-rc1. There is a proposed simplified fix by Tyler Hicks for - carnil> 4.19.y, 4.14.y. - carnil> Introduced in 1acfc104cdf8 ("drm/i915: Enable rcu-only context - carnil> lookups") in 4.14-rc1. -Bugs: -upstream: released (5.2-rc1) [7dc40713618c884bf07c030d1ab1f47a9dc1f310] -4.19-upstream-stable: released (4.19.97) [afb89cd5f2ba2d5d04b85b2692a9a3d86b6fabd7] -4.9-upstream-stable: N/A "Vulnerable code introduced later" -3.16-upstream-stable: N/A "Vulnerable code introduced later" -sid: released (5.2.6-1) -4.19-buster-security: released (4.19.98-1) -4.9-stretch-security: N/A "Vulnerable code introduced later" -3.16-jessie-security: N/A "Vulnerable code introduced later" |