diff options
| author | Salvatore Bonaccorso <carnil@debian.org> | 2022-03-25 20:49:54 +0100 |
|---|---|---|
| committer | Salvatore Bonaccorso <carnil@debian.org> | 2022-03-25 20:49:54 +0100 |
| commit | 799d3c586b6df4d41fccd5fc2ff796a087c26329 (patch) | |
| tree | 58859fea1691e870e5406a47cbb0c08c1e4582e6 /active/CVE-2021-20317 | |
| parent | e3e90ffdadf6bb9b0e7ff277a38879d594f49edd (diff) | |
Retire several CVEs
Diffstat (limited to 'active/CVE-2021-20317')
| -rw-r--r-- | active/CVE-2021-20317 | 17 |
1 files changed, 0 insertions, 17 deletions
diff --git a/active/CVE-2021-20317 b/active/CVE-2021-20317 deleted file mode 100644 index 44ec6985..00000000 --- a/active/CVE-2021-20317 +++ /dev/null @@ -1,17 +0,0 @@ -Description: lib/timerqueue: Rely on rbtree semantics for next timer -References: - https://bugzilla.redhat.com/show_bug.cgi?id=2005258 -Notes: - bwh> It's not totally clear what the bug is, but the code in 4.9 is - bwh> similar enough to 4.19 that I think it must also be affected. - bwh> For 4.9, commit cd9e61ed1eeb "rbtree: cache leftmost node internally" - bwh> needs to be applied first. -Bugs: -upstream: released (5.4-rc1) [511885d7061eda3eb1faf3f57dcc936ff75863f1] -5.10-upstream-stable: N/A "Fixed before branching point" -4.19-upstream-stable: released (4.19.210) [b9a1ac8e7c03fd09992352c7fb1a61cbbb9ad52b] -4.9-upstream-stable: released (4.9.298) [ef2e64035f074bfeef14c28347aaec0b486a9e9f] -sid: released (5.4.6-1) -5.10-bullseye-security: N/A "Fixed before branching point" -4.19-buster-security: released (4.19.232-1) -4.9-stretch-security: released (4.9.290-1) [bugfix/all/lib-timerqueue-rely-on-rbtree-semantics-for-next-tim.patch] |