summaryrefslogtreecommitdiffstats
path: root/active/CVE-2022-28389
diff options
context:
space:
mode:
authorSalvatore Bonaccorso <carnil@debian.org>2022-06-30 17:01:10 +0200
committerSalvatore Bonaccorso <carnil@debian.org>2022-06-30 21:55:46 +0200
commitff9e8ccc7b2059de19da5e9683e8a52ed21e5da5 (patch)
tree383b1cab382a5aa50d016e0d5a951bbc50b72b3d /active/CVE-2022-28389
parent427b0825286c5742924dc4102e0237f5359bcbef (diff)
Mark issues as released with the 4.19.249-1 upload
As debian/4.19.249-1 is tagged in git and uploaded (even though got a followup 4.19.249-2) go ahead and mark the CVEs accordingly affecting the 4.19.y series as released for 4.19.249-1.
Diffstat (limited to 'active/CVE-2022-28389')
-rw-r--r--active/CVE-2022-283892
1 files changed, 1 insertions, 1 deletions
diff --git a/active/CVE-2022-28389 b/active/CVE-2022-28389
index c2b5c0a71..983d813e7 100644
--- a/active/CVE-2022-28389
+++ b/active/CVE-2022-28389
@@ -11,5 +11,5 @@ upstream: released (5.18-rc1) [04c9b00ba83594a29813d6b1fb8fdc93a3915174]
4.9-upstream-stable: N/A "Vulnerable code not present"
sid: released (5.17.3-1)
5.10-bullseye-security: released (5.10.113-1)
-4.19-buster-security: needed
+4.19-buster-security: released (4.19.249-1)
4.9-stretch-security: N/A "Vulnerable code not present"

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