diff options
| author | Ben Hutchings <ben@decadent.org.uk> | 2024-03-11 00:11:29 +0100 |
|---|---|---|
| committer | Ben Hutchings <ben@decadent.org.uk> | 2024-03-11 00:11:29 +0100 |
| commit | 73dccfc63d792093db024dd1df1e7dfd4682bac2 (patch) | |
| tree | d35990e4681baf180c86d2f44a196d962c17f90a /active/CVE-2023-6536 | |
| parent | bbc0d50a98f15c31b7b55b353e25ec274555979c (diff) | |
Record various issues as already fixed upstream
Diffstat (limited to 'active/CVE-2023-6536')
| -rw-r--r-- | active/CVE-2023-6536 | 20 |
1 files changed, 12 insertions, 8 deletions
diff --git a/active/CVE-2023-6536 b/active/CVE-2023-6536 index b85dd1ef..e804453b 100644 --- a/active/CVE-2023-6536 +++ b/active/CVE-2023-6536 @@ -3,12 +3,16 @@ References: https://bugzilla.redhat.com/show_bug.cgi?id=2254052 https://lore.kernel.org/linux-nvme/69e7bbe4-b454-4941-90e2-2e6a4cf0f182@grimberg.me/T/#t Notes: + bwh> I think this is fixed by commit 0849a5441358 "nvmet-tcp: + bwh> fix a crash in nvmet_req_complete()"; that mentions + bwh> nvmet_req_complete() which is a thin wrapper for + bwh> __nvmet_req_complete()). 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) [0849a5441358cef02586fb2d60f707c0db195628] +6.1-upstream-stable: released (6.1.75) [83ccd15717ee2b6143df72df39685f0c832e3451] +5.10-upstream-stable: released (5.10.209) [39669fae69f302961d89f38d969c6fcc1d07eb02] +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 |