| Version | |
|---|---|
| uring.2.7.0 (latest) | |
| 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.7 | n/a | Unknown | CVE-2018-5953 | 8/7/2018 |
| linux-headers | uring.0.9 | n/a | Unknown | CVE-2018-5953 | 8/7/2018 |
| linux-headers | uring.0.8 | n/a | Unknown | CVE-2018-5953 | 8/7/2018 |
| linux-headers | uring.0.6 | n/a | Unknown | CVE-2018-5953 | 8/7/2018 |
| linux-headers | uring.0.4 | n/a | Unknown | CVE-2018-5953 | 8/7/2018 |
| linux-headers | uring.0.5 | n/a | Unknown | CVE-2018-5953 | 8/7/2018 |
| linux-headers | uring.0.1 | n/a | Unknown | CVE-2018-5953 | 8/7/2018 |
| linux-headers | uring.0.3 | n/a | Unknown | CVE-2018-5953 | 8/7/2018 |
| linux-headers | uring.2.7.0 | n/a | Unknown | CVE-2018-5953 | 8/7/2018 |
| linux-headers | uring.0.2 | n/a | Unknown | CVE-2018-5953 | 8/7/2018 |
| linux-headers | uring.2.7.0 | Qualcomm, Inc. | Unknown | CVE-2018-5873 | 7/6/2018 |
| linux-headers | uring.0.8 | Qualcomm, Inc. | Unknown | CVE-2018-5873 | 7/6/2018 |
| linux-headers | uring.0.9 | Qualcomm, Inc. | Unknown | CVE-2018-5873 | 7/6/2018 |
| linux-headers | uring.0.6 | Qualcomm, Inc. | Unknown | CVE-2018-5873 | 7/6/2018 |
| linux-headers | uring.0.5 | Qualcomm, Inc. | Unknown | CVE-2018-5873 | 7/6/2018 |
| linux-headers | uring.0.7 | Qualcomm, Inc. | Unknown | CVE-2018-5873 | 7/6/2018 |
| linux-headers | uring.0.2 | Qualcomm, Inc. | Unknown | CVE-2018-5873 | 7/6/2018 |
| linux-headers | uring.0.3 | Qualcomm, Inc. | Unknown | CVE-2018-5873 | 7/6/2018 |
| linux-headers | uring.0.1 | Qualcomm, Inc. | Unknown | CVE-2018-5873 | 7/6/2018 |
| linux-headers | uring.0.4 | Qualcomm, Inc. | Unknown | CVE-2018-5873 | 7/6/2018 |