Track CVE fixes released in 5.10.158-1 tagged version for bullseye-pu for 11.6

18 files changed, 18 insertions, 18 deletions

diff --git a/active/CVE-2021-3759 b/active/CVE-2021-3759
index f6ccbc51..85ef3af8 100644
--- a/active/CVE-2021-3759
+++ b/active/CVE-2021-3759
@@ -9,6 +9,6 @@ upstream: released (5.15-rc1) [18319498fdd4cdf8c1c2c48cd432863b1f915d6f]
 4.19-upstream-stable: needed
 4.9-upstream-stable: needed
 sid: released (5.15.3-1)
-5.10-bullseye-security: needed
+5.10-bullseye-security: released (5.10.158-1)
 4.19-buster-security: needed
 4.9-stretch-security: ignored "EOL"
diff --git a/active/CVE-2022-3169 b/active/CVE-2022-3169
index 8fecdb5b..9d4966d4 100644
--- a/active/CVE-2022-3169
+++ b/active/CVE-2022-3169
@@ -13,5 +13,5 @@ upstream: released (6.1-rc1) [1e866afd4bcdd01a70a5eddb4371158d3035ce03]
 5.10-upstream-stable: released (5.10.156) [023435a095d22bcbbaeea7e3a8c534b5c57d0d82]
 4.19-upstream-stable: needed
 sid: released (6.0.10-1)
-5.10-bullseye-security: needed
+5.10-bullseye-security: released (5.10.158-1)
 4.19-buster-security: needed
diff --git a/active/CVE-2022-3435 b/active/CVE-2022-3435
index ba6c022a..f3d2cc77 100644
--- a/active/CVE-2022-3435
+++ b/active/CVE-2022-3435
@@ -10,5 +10,5 @@ upstream: released (6.1-rc1) [61b91eb33a69c3be11b259c5ea484505cd79f883]
 5.10-upstream-stable: released (5.10.158) [0b5394229ebae09afc07aabccb5ffd705ffd250e]
 4.19-upstream-stable: N/A "Vulnerable code not present"
 sid: released (6.0.12-1)
-5.10-bullseye-security: needed
+5.10-bullseye-security: released (5.10.158-1)
 4.19-buster-security: N/A "Vulnerable code not present"
diff --git a/active/CVE-2022-3521 b/active/CVE-2022-3521
index 2239431e..7e35b3ee 100644
--- a/active/CVE-2022-3521
+++ b/active/CVE-2022-3521
@@ -9,5 +9,5 @@ upstream: released (6.1-rc1) [ec7eede369fe5b0d085ac51fdbb95184f87bfc6c]
 5.10-upstream-stable: released (5.10.156) [7deb7a9d33e4941c5ff190108146d3a56bf69e9d]
 4.19-upstream-stable: released (4.19.267) [23a0a5869749c7833772330313ae7aec6581ec60]
 sid: released (6.0.10-1)
-5.10-bullseye-security: needed
+5.10-bullseye-security: released (5.10.158-1)
 4.19-buster-security: pending (4.19.268-1)
diff --git a/active/CVE-2022-3524 b/active/CVE-2022-3524
index 2d2e5e85..b8fd6b43 100644
--- a/active/CVE-2022-3524
+++ b/active/CVE-2022-3524
@@ -7,5 +7,5 @@ upstream: released (6.1-rc1) [3c52c6bb831f6335c176a0fc7214e26f43adbd11]
 5.10-upstream-stable: released (5.10.154) [818c36b988b82f31e4be8ad8415e1be902b8e5f8]
 4.19-upstream-stable: released (4.19.268) [bbfbdca680b0cbea0e57be597b5e2cae19747052]
 sid: released (6.0.7-1)
-5.10-bullseye-security: needed
+5.10-bullseye-security: released (5.10.158-1)
 4.19-buster-security: pending (4.19.268-1)
diff --git a/active/CVE-2022-3535 b/active/CVE-2022-3535
index 3acc4f4a..d3fe8e46 100644
--- a/active/CVE-2022-3535
+++ b/active/CVE-2022-3535
@@ -7,5 +7,5 @@ upstream: released (6.1-rc1) [0152dfee235e87660f52a117fc9f70dc55956bb4]
 5.10-upstream-stable: released (5.10.150) [29f50bcf0f8b9e49c3c9b0e08fcae2ec3a88cc9f]
 4.19-upstream-stable: released (4.19.262) [84e2394b0be397f7198986aa9a28207f70b29bd4]
 sid: released (6.0.3-1)
-5.10-bullseye-security: needed
+5.10-bullseye-security: released (5.10.158-1)
 4.19-buster-security: pending (4.19.268-1)
diff --git a/active/CVE-2022-3542 b/active/CVE-2022-3542
index f95ca38f..e621af0b 100644
--- a/active/CVE-2022-3542
+++ b/active/CVE-2022-3542
@@ -7,5 +7,5 @@ upstream: released (6.1-rc1) [b43f9acbb8942b05252be83ac25a81cec70cc192]
 5.10-upstream-stable: released (5.10.150) [6cc0e2afc6a137d45b9523f61a1b1b16a68c9dc0]
 4.19-upstream-stable: released (4.19.262) [70421f9708d4cf14c2bd15de58862a3d22e00bbe]
 sid: released (6.0.3-1)
-5.10-bullseye-security: needed
+5.10-bullseye-security: released (5.10.158-1)
 4.19-buster-security: pending (4.19.268-1)
diff --git a/active/CVE-2022-3564 b/active/CVE-2022-3564
index 1623b1ae..e9a1cab1 100644
--- a/active/CVE-2022-3564
+++ b/active/CVE-2022-3564
@@ -7,5 +7,5 @@ upstream: released (6.1-rc4) [3aff8aaca4e36dc8b17eaa011684881a80238966]
 5.10-upstream-stable: released (5.10.154) [cb1c012099ef5904cd468bdb8d6fcdfdd9bcb569]
 4.19-upstream-stable: released (4.19.265) [6c7407bfbeafc80a04e6eaedcf34d378532a04f2]
 sid: released (6.0.8-1)
-5.10-bullseye-security: needed
+5.10-bullseye-security: released (5.10.158-1)
 4.19-buster-security: pending (4.19.268-1)
diff --git a/active/CVE-2022-3565 b/active/CVE-2022-3565
index 4eebff40..f9fc1811 100644
--- a/active/CVE-2022-3565
+++ b/active/CVE-2022-3565
@@ -7,5 +7,5 @@ upstream: released (6.1-rc1) [2568a7e0832ee30b0a351016d03062ab4e0e0a3f]
 5.10-upstream-stable: released (5.10.150) [2a1d0363208528a3bacbc2c37264d60182efd482]
 4.19-upstream-stable: released (4.19.262) [27f74a47d5b1cf52d48af15993bb1caa31ad8f5b]
 sid: released (6.0.3-1)
-5.10-bullseye-security: needed
+5.10-bullseye-security: released (5.10.158-1)
 4.19-buster-security: pending (4.19.268-1)
diff --git a/active/CVE-2022-3594 b/active/CVE-2022-3594
index 308dc9b1..0337fa03 100644
--- a/active/CVE-2022-3594
+++ b/active/CVE-2022-3594
@@ -7,5 +7,5 @@ upstream: released (6.1-rc1) [93e2be344a7db169b7119de21ac1bf253b8c6907]
 5.10-upstream-stable: released (5.10.150) [484400d433ca1903a87268c55f019e932297538a]
 4.19-upstream-stable: released (4.19.262) [88d2a93972c369eb812952aa15a25c1385506c1d]
 sid: released (6.0.3-1)
-5.10-bullseye-security: needed
+5.10-bullseye-security: released (5.10.158-1)
 4.19-buster-security: pending (4.19.268-1)
diff --git a/active/CVE-2022-3628 b/active/CVE-2022-3628
index c7176380..186a4145 100644
--- a/active/CVE-2022-3628
+++ b/active/CVE-2022-3628
@@ -11,5 +11,5 @@ upstream: released (6.1-rc5) [6788ba8aed4e28e90f72d68a9d794e34eac17295]
 5.10-upstream-stable: released (5.10.154) [c6678c8f4f3f8383fe2dff3455de3d504382638f]
 4.19-upstream-stable: released (4.19.265) [5e7d546917431400b7d6e5e38f588e0bd13083c9]
 sid: released (6.0.8-1)
-5.10-bullseye-security: needed
+5.10-bullseye-security: released (5.10.158-1)
 4.19-buster-security: pending (4.19.268-1)
diff --git a/active/CVE-2022-3640 b/active/CVE-2022-3640
index b00564ec..59855afa 100644
--- a/active/CVE-2022-3640
+++ b/active/CVE-2022-3640
@@ -10,5 +10,5 @@ upstream: released (6.1-rc4) [0d0e2d032811280b927650ff3c15fe5020e82533]
 5.10-upstream-stable: released (5.10.154) [d9ec6e2fbd4a565b2345d4852f586b7ae3ab41fd]
 4.19-upstream-stable: released (4.19.265) [7f7bfdd9a9af3b12c33d9da9a012e7f4d5c91f4b]
 sid: released (6.0.8-1)
-5.10-bullseye-security: needed
+5.10-bullseye-security: released (5.10.158-1)
 4.19-buster-security: pending (4.19.268-1)
diff --git a/active/CVE-2022-4139 b/active/CVE-2022-4139
index db248f42..cd09671f 100644
--- a/active/CVE-2022-4139
+++ b/active/CVE-2022-4139
@@ -14,5 +14,5 @@ upstream: released (6.1-rc8) [04aa64375f48a5d430b5550d9271f8428883e550]
 5.10-upstream-stable: released (5.10.157) [86f0082fb9470904b15546726417f28077088fee]
 4.19-upstream-stable: N/A "Vulnerability not present"
 sid: released (6.0.10-2) [bugfix/x86/drm-i915-fix-TLB-invalidation-for-Gen12-video-and-co.patch]
-5.10-bullseye-security: needed
+5.10-bullseye-security: released (5.10.158-1)
 4.19-buster-security: N/A "Vulnerability not present"
diff --git a/active/CVE-2022-41849 b/active/CVE-2022-41849
index ad0257a0..2cda5460 100644
--- a/active/CVE-2022-41849
+++ b/active/CVE-2022-41849
@@ -7,5 +7,5 @@ upstream: released (6.1-rc1) [5610bcfe8693c02e2e4c8b31427f1bdbdecc839c]
 5.10-upstream-stable: released (5.10.150) [e50472949604f385e09ce3fa4e74dce9f44fb19b]
 4.19-upstream-stable: released (4.19.262) [6d8dbefc4de96d35d68c723e2e75b5a23173c08c]
 sid: released (6.0.3-1)
-5.10-bullseye-security: needed
+5.10-bullseye-security: released (5.10.158-1)
 4.19-buster-security: pending (4.19.268-1)
diff --git a/active/CVE-2022-41850 b/active/CVE-2022-41850
index 11d57f17..6b5519d9 100644
--- a/active/CVE-2022-41850
+++ b/active/CVE-2022-41850
@@ -7,5 +7,5 @@ upstream: released (6.1-rc1) [cacdb14b1c8d3804a3a7d31773bc7569837b71a4]
 5.10-upstream-stable: released (5.10.150) [dbcca76435a606a352c794956e6df62eedd3a353]
 4.19-upstream-stable: released (4.19.262) [13de81c7ea0fd68efb48a2d2957e349237905923]
 sid: released (6.0.3-1)
-5.10-bullseye-security: needed
+5.10-bullseye-security: released (5.10.158-1)
 4.19-buster-security: pending (4.19.268-1)
diff --git a/active/CVE-2022-42895 b/active/CVE-2022-42895
index 588af384..e88561c4 100644
--- a/active/CVE-2022-42895
+++ b/active/CVE-2022-42895
@@ -9,5 +9,5 @@ upstream: released (6.1-rc4) [b1a2cd50c0357f243b7435a732b4e62ba3157a2e]
 5.10-upstream-stable: released (5.10.154) [26ca2ac091b49281d73df86111d16e5a76e43bd7]
 4.19-upstream-stable: released (4.19.265) [36919a82f335784d86b4def308739559bb47943d]
 sid: released (6.0.7-1) [bugfix/all/Bluetooth-L2CAP-Fix-attempting-to-access-uninitializ.patch]
-5.10-bullseye-security: needed
+5.10-bullseye-security: released (5.10.158-1)
 4.19-buster-security: pending (4.19.268-1)
diff --git a/active/CVE-2022-42896 b/active/CVE-2022-42896
index 114c0bd1..5b269546 100644
--- a/active/CVE-2022-42896
+++ b/active/CVE-2022-42896
@@ -9,5 +9,5 @@ upstream: released (6.1-rc4) [711f8c3fb3db61897080468586b970c87c61d9e4]
 5.10-upstream-stable: released (5.10.154) [6b6f94fb9a74dd2891f11de4e638c6202bc89476]
 4.19-upstream-stable: released (4.19.268) [a2045d57e844864605d39e6cfd2237861d800f13]
 sid: released (6.0.7-1) [bugfix/all/Bluetooth-L2CAP-Fix-accepting-connection-request-for.patch]
-5.10-bullseye-security: needed
+5.10-bullseye-security: released (5.10.158-1)
 4.19-buster-security: pending (4.19.268-1)
diff --git a/active/CVE-2022-4378 b/active/CVE-2022-4378
index a390f2fa..45947b18 100644
--- a/active/CVE-2022-4378
+++ b/active/CVE-2022-4378
@@ -7,5 +7,5 @@ upstream: released (6.1) [bce9332220bd677d83b19d21502776ad555a0e73, e6cfaf34be9f
 5.10-upstream-stable: released (5.10.158) [9ba389863ac63032d4b6ffad2c90a62cd78082ee, 4aa32aaef6c1b5e39ae2508ec596bd7b67871043]
 4.19-upstream-stable: released (4.19.268) [a9c309fb49ffe3203f948973fd27b8f64f7f30c4, fe84d7f0cb66d150de094fba461f0cb5d5b12c85]
 sid: released (6.0.12-1)
-5.10-bullseye-security: needed
+5.10-bullseye-security: released (5.10.158-1)
 4.19-buster-security: pending (4.19.268-1)