VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
290392 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-47183 | suse_vex | SUSE CVE CVE-2025-47183 | known affected: 54 recommended: 53 | 2026-08-01T17:06:29+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-68781 | suse_vex | SUSE CVE CVE-2025-68781 | known not affected: 357 | 2026-08-01T17:05:42+00:00 | Vulnerability · Source |
| CVE-2025-69419 | suse_vex | SUSE CVE CVE-2025-69419 | known affected: 406 known not affected: 251 recommended: 334 | 2026-08-01T17:05:36+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 |
| CVE-2026-0650 | suse_vex | SUSE CVE CVE-2026-0650 | No product status | 2026-08-01T17:05:29+00:00 | Vulnerability · Source |
| CVE-2025-71293 | redhat_vex | kernel: drm/amdgpu/ras: Move ras data alloc before bad page check | known affected: 274 | 2026-08-01T16:58:25+00:00 | Vulnerability · Source |
| CVE-2026-22687 | suse_vex | SUSE CVE CVE-2026-22687 | No product status | 2026-08-01T16:54:24+00:00 | Vulnerability · Source |
| CVE-2026-22862 | suse_vex | SUSE CVE CVE-2026-22862 | No product status | 2026-08-01T16:54:20+00:00 | Vulnerability · Source |
| CVE-2026-22868 | suse_vex | SUSE CVE CVE-2026-22868 | No product status | 2026-08-01T16:54:18+00:00 | Vulnerability · Source |
| CVE-2026-28377 | suse_vex | SUSE CVE CVE-2026-28377 | recommended: 1 | 2026-08-01T16:53:51+00:00 | Vulnerability · Source |
| CVE-2026-33757 | suse_vex | SUSE CVE CVE-2026-33757 | recommended: 8 | 2026-08-01T16:53:29+00:00 | Vulnerability · Source |
| CVE-2026-33758 | suse_vex | SUSE CVE CVE-2026-33758 | recommended: 8 | 2026-08-01T16:53:27+00:00 | Vulnerability · Source |
| CVE-2026-33813 | suse_vex | SUSE CVE CVE-2026-33813 | recommended: 12 | 2026-08-01T16:53:25+00:00 | Vulnerability · Source |
| CVE-2026-34165 | suse_vex | SUSE CVE CVE-2026-34165 | recommended: 1 | 2026-08-01T16:53:22+00:00 | Vulnerability · Source |
| CVE-2026-39824 | suse_vex | SUSE CVE CVE-2026-39824 | recommended: 17 | 2026-08-01T16:53:03+00:00 | Vulnerability · Source |
| CVE-2026-42500 | suse_vex | SUSE CVE CVE-2026-42500 | recommended: 9 | 2026-08-01T16:52:29+00:00 | Vulnerability · Source |
| CVE-2026-45570 | suse_vex | SUSE CVE CVE-2026-45570 | recommended: 4 | 2026-08-01T16:51:54+00:00 | Vulnerability · Source |
| CVE-2026-45711 | suse_vex | SUSE CVE CVE-2026-45711 | No product status | 2026-08-01T16:51:52+00:00 | Vulnerability · Source |
| CVE-2026-47722 | suse_vex | SUSE CVE CVE-2026-47722 | No product status | 2026-08-01T16:51:26+00:00 | Vulnerability · Source |
| CVE-2026-47723 | suse_vex | SUSE CVE CVE-2026-47723 | No product status | 2026-08-01T16:51:24+00:00 | Vulnerability · Source |
| CVE-2026-47725 | suse_vex | SUSE CVE CVE-2026-47725 | No product status | 2026-08-01T16:51:21+00:00 | Vulnerability · Source |
| CVE-2026-47726 | suse_vex | SUSE CVE CVE-2026-47726 | No product status | 2026-08-01T16:51:19+00:00 | Vulnerability · Source |
| CVE-2026-48058 | suse_vex | SUSE CVE CVE-2026-48058 | No product status | 2026-08-01T16:51:16+00:00 | Vulnerability · Source |
| CVE-2026-52807 | suse_vex | SUSE CVE CVE-2026-52807 | No product status | 2026-08-01T16:50:54+00:00 | Vulnerability · Source |
| CVE-2026-53046 | suse_vex | SUSE CVE CVE-2026-53046 | known affected: 112 known not affected: 179 | 2026-08-01T16:50:48+00:00 | Vulnerability · Source |
| CVE-2026-56379 | suse_vex | SUSE CVE CVE-2026-56379 | first fixed: 148 known affected: 72 recommended: 249 | 2026-08-01T16:50:13+00:00 | Vulnerability · Source |
| CVE-2026-58586 | suse_vex | SUSE CVE CVE-2026-58586 | No product status | 2026-08-01T16:50:01+00:00 | Vulnerability · Source |
| CVE-2026-62574 | suse_vex | SUSE CVE CVE-2026-62574 | known not affected: 476 | 2026-08-01T16:49:59+00:00 | Vulnerability · Source |
| CVE-2026-43318 | redhat_vex | kernel: drm/amdgpu: fix sync handling in amdgpu_dma_buf_move_notify | known affected: 198 known not affected: 76 | 2026-08-01T16:43:28+00:00 | Vulnerability · Source |
| CVE-2026-43398 | redhat_vex | kernel: drm/amdgpu: add upper bound check on user inputs in wait ioctl | known affected: 274 | 2026-08-01T16:28:24+00:00 | Vulnerability · Source |
| CVE-2026-43399 | redhat_vex | kernel: drm/amdgpu/userq: Fix reference leak in amdgpu_userq_wait_ioctl | known affected: 198 known not affected: 76 | 2026-08-01T16:23:25+00:00 | Vulnerability · Source |
| CVE-2026-43400 | redhat_vex | kernel: drm/amdgpu: add upper bound check on user inputs in signal ioctl | known affected: 274 | 2026-08-01T16:18:45+00:00 | Vulnerability · Source |
| CVE-2026-45853 | redhat_vex | kernel: drm/amdgpu: Use kvfree instead of kfree in amdgpu_gmc_get_nps_memranges() | known affected: 198 known not affected: 76 | 2026-08-01T15:58:43+00:00 | Vulnerability · Source |
| CVE-2026-46199 | redhat_vex | kernel: drm/amdgpu/vcn4: Prevent OOB reads when parsing dec msg | known affected: 274 | 2026-08-01T15:33:41+00:00 | Vulnerability · Source |
| CVE-2026-46217 | redhat_vex | kernel: drm/amdgpu/vcn4: Avoid overflow on msg bound check | known affected: 14 known not affected: 260 | 2026-08-01T14:25:45+00:00 | Vulnerability · Source |
| CVE-2026-46218 | redhat_vex | kernel: drm/amdgpu: Add bounds checking to ib_{get,set}_value | known not affected: 274 | 2026-08-01T14:20:04+00:00 | Vulnerability · Source |
| CVE-2026-46229 | redhat_vex | kernel: drm/amdkfd: Clear VRAM on allocation to prevent stale data exposure | known affected: 274 | 2026-08-01T14:13:22+00:00 | Vulnerability · Source |
| CVE-2026-46220 | redhat_vex | kernel: drm/amdgpu/sdma4: replace BUG_ON with WARN_ON in fence emission | known affected: 246 known not affected: 28 | 2026-08-01T14:13:22+00:00 | Vulnerability · Source |
| CVE-2026-46197 | redhat_vex | kernel: drm/amdkfd: validate SVM ioctl nattr against buffer size | known affected: 274 | 2026-08-01T13:58:22+00:00 | Vulnerability · Source |
| CVE-2026-46245 | redhat_vex | kernel: drm/amd/display: Fix dc_link NULL handling in HPD init | known affected: 246 known not affected: 28 | 2026-08-01T13:43:55+00:00 | Vulnerability · Source |
| CVE-2026-46263 | redhat_vex | kernel: drm/amd/display: Fix out-of-bounds stream encoder index v3 | known affected: 198 known not affected: 76 | 2026-08-01T13:38:38+00:00 | Vulnerability · Source |
| CVE-2026-46311 | redhat_vex | kernel: drm/amdgpu/userq: fix access to stale wptr mapping | known affected: 274 | 2026-08-01T13:33:55+00:00 | Vulnerability · Source |
| CVE-2026-46276 | redhat_vex | kernel: drm/amdgpu: fix zero-size GDS range init on RDNA4 | known affected: 274 | 2026-08-01T13:33:47+00:00 | Vulnerability · Source |
| CVE-2026-52987 | redhat_vex | kernel: drm/amdgpu: avoid double drm_exec_fini() in userq validate | known affected: 184 known not affected: 76 under investigation: 14 | 2026-08-01T13:23:22+00:00 | Vulnerability · Source |
| CVE-2026-63842 | redhat_vex | kernel: drm/amdgpu/jpeg: set no_user_fence for JPEG v5.0.0 ring | known affected: 198 known not affected: 76 | 2026-08-01T07:03:20+00:00 | Vulnerability · Source |
| CVE-2026-57053 | redhat_vex | libidn: GNU libidn: Out-of-bounds read in ToUnicode APIs | fixed: 3 known affected: 8 known not affected: 10 | 2026-08-01T03:45:47+00:00 | Vulnerability · Source |
| CVE-2005-3390 | suse_vex | SUSE CVE CVE-2005-3390 | known affected: 2110 recommended: 201 | 2026-08-01T00:28:21+00:00 | Vulnerability · Source |
| CVE-2006-4227 | suse_vex | SUSE CVE CVE-2006-4227 | known not affected: 44 recommended: 176 | 2026-08-01T00:28:18+00:00 | Vulnerability · Source |