summaryrefslogtreecommitdiffstats
path: root/active/CVE-2023-6356
diff options
context:
space:
mode:
authorBen Hutchings <ben@decadent.org.uk>2024-03-11 00:11:29 +0100
committerBen Hutchings <ben@decadent.org.uk>2024-03-11 00:11:29 +0100
commit73dccfc63d792093db024dd1df1e7dfd4682bac2 (patch)
treed35990e4681baf180c86d2f44a196d962c17f90a /active/CVE-2023-6356
parentbbc0d50a98f15c31b7b55b353e25ec274555979c (diff)
Record various issues as already fixed upstream
Diffstat (limited to 'active/CVE-2023-6356')
-rw-r--r--active/CVE-2023-635621
1 files changed, 13 insertions, 8 deletions
diff --git a/active/CVE-2023-6356 b/active/CVE-2023-6356
index 6b346475..2617a7b8 100644
--- a/active/CVE-2023-6356
+++ b/active/CVE-2023-6356
@@ -3,12 +3,17 @@ References:
https://bugzilla.redhat.com/show_bug.cgi?id=2254054
https://lore.kernel.org/linux-nvme/CAK5usQupQgYoyav2itYADv2XVooMptqqswW8cTkuoMkRpjapwQ@mail.gmail.com/T/#t
Notes:
+ bwh> There has never been a nvmet_tcp_build_iovec() function in
+ bwh> nvmet, but I think this is fixed by commit efa56305908b
+ bwh> "nvmet-tcp: Fix a kernel panic when host sends an invalid
+ bwh> H2C PDU length" which mentions nvmet_tcp_build_pdu_iovec().
+ bwh> Fixed as well in 6.6.14 and 6.7.2.
Bugs:
-upstream:
-6.1-upstream-stable:
-5.10-upstream-stable:
-4.19-upstream-stable:
-sid:
-6.1-bookworm-security:
-5.10-bullseye-security:
-4.19-buster-security:
+upstream: released (6.8-rc1) [efa56305908ba20de2104f1b8508c6a7401833be]
+6.1-upstream-stable: released (6.1.75) [2871aa407007f6f531fae181ad252486e022df42]
+5.10-upstream-stable: released (5.10.209) [f775f2621c2ac5cc3a0b3a64665dad4fb146e510]
+4.19-upstream-stable: needed
+sid: released (6.6.15-1)
+6.1-bookworm-security: released (6.1.76-1)
+5.10-bullseye-security: released (5.10.209-1)
+4.19-buster-security: needed

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