| 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.5 | n/a | Unknown | CVE-2019-10638 | 7/5/2019 |
| linux-headers | uring.2.15.0 | n/a | Unknown | CVE-2019-10638 | 7/5/2019 |
| linux-headers | uring.0.7 | n/a | Unknown | CVE-2019-10638 | 7/5/2019 |
| linux-headers | uring.0.4 | n/a | Unknown | CVE-2019-10638 | 7/5/2019 |
| linux-headers | uring.0.8 | n/a | Unknown | CVE-2019-10638 | 7/5/2019 |
| linux-headers | uring.2.7.0 | n/a | Unknown | CVE-2019-10638 | 7/5/2019 |
| linux-headers | uring.2.7.0 | SUSE | High | CVE-2019-10220 | 11/27/2019 |
| linux-headers | uring.0.9 | SUSE | High | CVE-2019-10220 | 11/27/2019 |
| linux-headers | uring.0.2 | SUSE | High | CVE-2019-10220 | 11/27/2019 |
| linux-headers | uring.2.15.1 | SUSE | High | CVE-2019-10220 | 11/27/2019 |
| linux-headers | uring.0.3 | SUSE | High | CVE-2019-10220 | 11/27/2019 |
| linux-headers | uring.0.1 | SUSE | High | CVE-2019-10220 | 11/27/2019 |
| linux-headers | uring.0.6 | SUSE | High | CVE-2019-10220 | 11/27/2019 |
| linux-headers | uring.2.14.0 | SUSE | High | CVE-2019-10220 | 11/27/2019 |
| linux-headers | uring.0.8 | SUSE | High | CVE-2019-10220 | 11/27/2019 |
| linux-headers | uring.0.7 | SUSE | High | CVE-2019-10220 | 11/27/2019 |
| linux-headers | uring.0.5 | SUSE | High | CVE-2019-10220 | 11/27/2019 |
| linux-headers | uring.2.15.0 | SUSE | High | CVE-2019-10220 | 11/27/2019 |
| linux-headers | uring.0.4 | SUSE | High | CVE-2019-10220 | 11/27/2019 |
| linux-headers | uring.0.4 | Red Hat | Medium | CVE-2019-10207 | 11/25/2019 |