| Version | |
|---|---|
| uring.2.7.0 (latest) | |
| uring.2.15.1 | |
| uring.2.15.0 | |
| uring.2.14.0 | |
| uring.0.9 | |
| uring.0.8 | |
| uring.0.7 | |
| uring.0.6 | |
| uring.0.5 | |
| uring.0.4 | |
| uring.0.3 | |
| uring.0.2 | |
| uring.0.1 |
| Product | For package | Vendor | Severity | CVE | Published |
|---|---|---|---|---|---|
| linux-headers | uring.0.8 | n/a | Unknown | CVE-2020-8428 | 1/28/2020 |
| linux-headers | uring.0.2 | n/a | Unknown | CVE-2020-8428 | 1/28/2020 |
| linux-headers | uring.0.7 | n/a | Unknown | CVE-2020-8428 | 1/28/2020 |
| linux-headers | uring.2.15.0 | n/a | Unknown | CVE-2020-8428 | 1/28/2020 |
| linux-headers | uring.2.14.0 | n/a | Unknown | CVE-2020-8428 | 1/28/2020 |
| linux-headers | uring.2.14.0 | n/a | Unknown | CVE-2020-7053 | 1/14/2020 |
| linux-headers | uring.2.7.0 | n/a | Unknown | CVE-2020-7053 | 1/14/2020 |
| linux-headers | uring.0.9 | n/a | Unknown | CVE-2020-7053 | 1/14/2020 |
| linux-headers | uring.0.6 | n/a | Unknown | CVE-2020-7053 | 1/14/2020 |
| linux-headers | uring.0.5 | n/a | Unknown | CVE-2020-7053 | 1/14/2020 |
| linux-headers | uring.0.4 | n/a | Unknown | CVE-2020-7053 | 1/14/2020 |
| linux-headers | uring.0.1 | n/a | Unknown | CVE-2020-7053 | 1/14/2020 |
| linux-headers | uring.0.3 | n/a | Unknown | CVE-2020-7053 | 1/14/2020 |
| linux-headers | uring.2.15.0 | n/a | Unknown | CVE-2020-7053 | 1/14/2020 |
| linux-headers | uring.0.2 | n/a | Unknown | CVE-2020-7053 | 1/14/2020 |
| linux-headers | uring.2.15.1 | n/a | Unknown | CVE-2020-7053 | 1/14/2020 |
| linux-headers | uring.0.8 | n/a | Unknown | CVE-2020-7053 | 1/14/2020 |
| linux-headers | uring.0.7 | n/a | Unknown | CVE-2020-7053 | 1/14/2020 |
| linux-headers | uring.0.7 | Linux | High | CVE-2020-36791 - net_sched: keep alloc_hash updated after hash allocation | 5/7/2025 |
| linux-headers | uring.0.1 | Linux | High | CVE-2020-36791 - net_sched: keep alloc_hash updated after hash allocation | 5/7/2025 |