diff options
| author | Moritz Muehlenhoff <jmm@debian.org> | 2022-12-14 17:15:47 +0100 |
|---|---|---|
| committer | Moritz Muehlenhoff <jmm@debian.org> | 2022-12-14 17:15:47 +0100 |
| commit | 076e33b11cfc62c1c654defb017643e6507b8a02 (patch) | |
| tree | 5799054f18e4f9c25d9a68906a0243a15dfd636b /retired/CVE-2022-3103 | |
| parent | 22bdf8e6c8ade20718e77f8a7361482a4072d612 (diff) | |
retire issues
Diffstat (limited to 'retired/CVE-2022-3103')
| -rw-r--r-- | retired/CVE-2022-3103 | 15 |
1 files changed, 15 insertions, 0 deletions
diff --git a/retired/CVE-2022-3103 b/retired/CVE-2022-3103 new file mode 100644 index 00000000..50dc88fc --- /dev/null +++ b/retired/CVE-2022-3103 @@ -0,0 +1,15 @@ +Description: io_uring: fix off-by-one in sync cancelation file check +References: +Notes: + carnil> The CVE entry is quite unclear, and just references the 6.0-rc3 + carnil> tag. I suspect 47abea041f89 ("io_uring: fix off-by-one in sync + carnil> cancelation file check") is the targetted off-by-one issue. + carnil> Then this though only fixes 78a861b94959 ("io_uring: add sync + carnil> cancelation API through io_uring_register()") in 6.0-rc1. +Bugs: +upstream: released (6.0-rc3) [47abea041f897d64dbd5777f0cf7745148f85d75] +5.10-upstream-stable: N/A "Vulnerable code not present" +4.19-upstream-stable: N/A "Vulnerable code not present" +sid: N/A "Vulnerable code not present" +5.10-bullseye-security: N/A "Vulnerable code not present" +4.19-buster-security: N/A "Vulnerable code not present" |