VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
293996 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2018-19622 | suse_vex | SUSE CVE CVE-2018-19622 | known affected: 111 known not affected: 37 recommended: 925 | 2026-08-01T23:34:14+00:00 | Vulnerability · Source |
| CVE-2018-20784 | suse_vex | SUSE CVE CVE-2018-20784 | known not affected: 491 recommended: 137 | 2026-08-01T23:34:09+00:00 | Vulnerability · Source |
| CVE-2018-21258 | suse_vex | SUSE CVE CVE-2018-21258 | No product status | 2026-08-01T23:34:08+00:00 | Vulnerability · Source |
| CVE-2018-25020 | suse_vex | SUSE CVE CVE-2018-25020 | known affected: 433 known not affected: 238 recommended: 438 | 2026-08-01T23:34:06+00:00 | Vulnerability · Source |
| CVE-2019-3018 | suse_vex | SUSE CVE CVE-2019-3018 | known affected: 13 known not affected: 121 recommended: 10 | 2026-08-01T23:33:59+00:00 | Vulnerability · Source |
| CVE-2019-3560 | suse_vex | SUSE CVE CVE-2019-3560 | recommended: 204 | 2026-08-01T23:33:58+00:00 | Vulnerability · Source |
| CVE-2019-4732 | suse_vex | SUSE CVE CVE-2019-4732 | known affected: 423 recommended: 311 | 2026-08-01T23:33:54+00:00 | Vulnerability · Source |
| CVE-2019-9457 | suse_vex | SUSE CVE CVE-2019-9457 | known affected: 6 known not affected: 256 | 2026-08-01T23:33:47+00:00 | Vulnerability · Source |
| CVE-2019-9857 | suse_vex | SUSE CVE CVE-2019-9857 | known not affected: 335 | 2026-08-01T23:33:41+00:00 | Vulnerability · Source |
| CVE-2019-9948 | suse_vex | SUSE CVE CVE-2019-9948 | known affected: 458 known not affected: 289 recommended: 834 | 2026-08-01T23:33:40+00:00 | Vulnerability · Source |
| CVE-2019-11486 | suse_vex | SUSE CVE CVE-2019-11486 | known affected: 107 known not affected: 21 recommended: 841 | 2026-08-01T23:33:34+00:00 | Vulnerability · Source |
| CVE-2019-14899 | suse_vex | SUSE CVE CVE-2019-14899 | known not affected: 371 | 2026-08-01T23:33:27+00:00 | Vulnerability · Source |
| CVE-2019-16714 | suse_vex | SUSE CVE CVE-2019-16714 | known not affected: 223 | 2026-08-01T23:33:21+00:00 | Vulnerability · Source |
| CVE-2019-17624 | suse_vex | SUSE CVE CVE-2019-17624 | known affected: 40 known not affected: 71 | 2026-08-01T23:33:20+00:00 | Vulnerability · Source |
| CVE-2019-19449 | suse_vex | SUSE CVE CVE-2019-19449 | known not affected: 459 | 2026-08-01T23:33:11+00:00 | Vulnerability · Source |
| CVE-2019-20382 | suse_vex | SUSE CVE CVE-2019-20382 | known affected: 196 known not affected: 180 recommended: 505 | 2026-08-01T23:33:09+00:00 | Vulnerability · Source |
| CVE-2020-0030 | suse_vex | SUSE CVE CVE-2020-0030 | known not affected: 204 | 2026-08-01T23:33:07+00:00 | Vulnerability · Source |
| CVE-2020-10134 | suse_vex | SUSE CVE CVE-2020-10134 | known affected: 3 | 2026-08-01T23:32:57+00:00 | Vulnerability · Source |
| CVE-2020-13791 | suse_vex | SUSE CVE CVE-2020-13791 | known not affected: 538 | 2026-08-01T23:32:48+00:00 | Vulnerability · Source |
| CVE-2020-25624 | suse_vex | SUSE CVE CVE-2020-25624 | known affected: 388 known not affected: 587 recommended: 850 | 2026-08-01T23:32:36+00:00 | Vulnerability · Source |
| CVE-2020-29443 | suse_vex | SUSE CVE CVE-2020-29443 | known affected: 388 known not affected: 146 recommended: 854 | 2026-08-01T23:32:27+00:00 | Vulnerability · Source |
| CVE-2020-36227 | suse_vex | SUSE CVE CVE-2020-36227 | known affected: 298 recommended: 854 | 2026-08-01T23:32:25+00:00 | Vulnerability · Source |
| CVE-2021-3770 | suse_vex | SUSE CVE CVE-2021-3770 | known not affected: 160 | 2026-08-01T23:32:16+00:00 | Vulnerability · Source |
| CVE-2021-46916 | suse_vex | SUSE CVE CVE-2021-46916 | known not affected: 312 | 2026-08-01T23:31:57+00:00 | Vulnerability · Source |
| CVE-2021-46970 | suse_vex | SUSE CVE CVE-2021-46970 | known not affected: 292 | 2026-08-01T23:31:56+00:00 | Vulnerability · Source |
| CVE-2025-2843 | redhat_vex | observability-operator: Observability Operator privilege escalation | fixed: 4 known not affected: 77 | 2026-08-01T19:50:42+00:00 | Vulnerability · Source |
| CVE-2026-23034 | redhat_vex | kernel: drm/amdgpu/userq: Fix fence reference leak on queue teardown v2 | known affected: 198 known not affected: 76 | 2026-08-01T18:08:30+00:00 | Vulnerability · Source |
| CVE-2026-23163 | redhat_vex | kernel: drm/amdgpu: fix NULL pointer dereference in amdgpu_gmc_filter_faults_remove | known affected: 198 known not affected: 76 | 2026-08-01T17:58:26+00:00 | Vulnerability · Source |
| CVE-2026-23213 | redhat_vex | kernel: drm/amd/pm: Disable MMIO access during SMU Mode 1 reset | known affected: 274 | 2026-08-01T17:53:34+00:00 | Vulnerability · Source |
| CVE-2026-23338 | redhat_vex | kernel: drm/amdgpu/userq: Do not allow userspace to trivially triger kernel warnings | known affected: 198 known not affected: 76 | 2026-08-01T17:48:43+00:00 | Vulnerability · Source |
| CVE-2026-31462 | redhat_vex | kernel: drm/amdgpu: prevent immediate PASID reuse case | known affected: 274 | 2026-08-01T17:33:29+00:00 | Vulnerability · Source |
| CVE-2026-31765 | redhat_vex | kernel: drm/amdgpu: Change AMDGPU_VA_RESERVED_TRAP_SIZE to 64KB | known affected: 184 known not affected: 90 | 2026-08-01T17:28:44+00:00 | Vulnerability · Source |
| CVE-2021-0961 | suse_vex | SUSE CVE CVE-2021-0961 | known not affected: 365 | 2026-08-01T17:13:43+00:00 | Vulnerability · Source |
| CVE-2021-26934 | suse_vex | SUSE CVE CVE-2021-26934 | known not affected: 345 | 2026-08-01T17:13:24+00:00 | Vulnerability · Source |
| CVE-2021-36978 | suse_vex | SUSE CVE CVE-2021-36978 | known affected: 7 recommended: 133 | 2026-08-01T17:13:09+00:00 | Vulnerability · Source |
| CVE-2021-47064 | suse_vex | SUSE CVE CVE-2021-47064 | known not affected: 292 | 2026-08-01T17:12:55+00:00 | Vulnerability · Source |
| CVE-2022-29885 | suse_vex | SUSE CVE CVE-2022-29885 | known not affected: 101 | 2026-08-01T17:11:36+00:00 | Vulnerability · Source |
| CVE-2022-34475 | suse_vex | SUSE CVE CVE-2022-34475 | known affected: 1 recommended: 365 | 2026-08-01T17:11:33+00:00 | Vulnerability · Source |
| CVE-2022-49582 | suse_vex | SUSE CVE CVE-2022-49582 | known not affected: 352 | 2026-08-01T17:10:37+00:00 | Vulnerability · Source |
| CVE-2022-50461 | suse_vex | SUSE CVE CVE-2022-50461 | known affected: 55 known not affected: 361 | 2026-08-01T17:10:15+00:00 | Vulnerability · Source |
| CVE-2023-20584 | suse_vex | SUSE CVE CVE-2023-20584 | known not affected: 325 recommended: 38 | 2026-08-01T17:09:55+00:00 | Vulnerability · Source |
| CVE-2023-52978 | suse_vex | SUSE CVE CVE-2023-52978 | known affected: 55 known not affected: 289 | 2026-08-01T17:09:24+00:00 | Vulnerability · Source |
| CVE-2026-43195 | redhat_vex | kernel: drm/amdgpu: validate user queue size constraints | known affected: 274 | 2026-08-01T17:08:30+00:00 | Vulnerability · Source |
| CVE-2025-13324 | suse_vex | SUSE CVE CVE-2025-13324 | No product status | 2026-08-01T17:07:22+00:00 | Vulnerability · Source |
| CVE-2025-14986 | suse_vex | SUSE CVE CVE-2025-14986 | No product status | 2026-08-01T17:07:18+00:00 | Vulnerability · Source |
| CVE-2025-14987 | suse_vex | SUSE CVE CVE-2025-14987 | No product status | 2026-08-01T17:07:17+00:00 | Vulnerability · Source |
| CVE-2025-21840 | suse_vex | SUSE CVE CVE-2025-21840 | known affected: 57 known not affected: 295 | 2026-08-01T17:07:11+00:00 | Vulnerability · Source |
| CVE-2025-59342 | suse_vex | SUSE CVE CVE-2025-59342 | recommended: 1 | 2026-08-01T17:06:17+00:00 | Vulnerability · Source |
| CVE-2025-68388 | suse_vex | SUSE CVE CVE-2025-68388 | No product status | 2026-08-01T17:05:44+00:00 | Vulnerability · Source |
| CVE-2025-71408 | suse_vex | SUSE CVE CVE-2025-71408 | recommended: 1 | 2026-08-01T17:05:31+00:00 | Vulnerability · Source |